1. 08 Feb, 2017 1 commit
  2. 09 Oct, 2016 1 commit
  3. 19 Sep, 2016 1 commit
  4. 21 Aug, 2014 1 commit
    • Masahiro Yamada's avatar
      tools, scripts: refactor error-out statements of Python scripts · 31e2141d
      Masahiro Yamada authored
      In Python, sys.exit() function can also take an object other
      than an integer.
      
      If an integer is given to the argument, Python exits with the return
      code of it.  If a non-integer argument is given, Python outputs it
      to stderr and exits with the return code of 1.
      
      That means,
      
          print >> sys.stderr, "Blah Blah"
          sys.exit(1)
      
      is equivalent to
      
          sys.exit("Blah Blah")
      
      The latter is a useful shorthand.
      
      Note:
      Some error messages in Buildman and Patman were output to stdout.
      But they should go to stderr.  They are also fixed by this commit.
      This is a nice side effect.
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      Acked-by: default avatarSimon Glass <sjg@chromium.org>
      31e2141d
  5. 24 Jul, 2013 1 commit
  6. 04 Apr, 2013 1 commit
  7. 31 Jan, 2013 2 commits
  8. 15 Oct, 2012 1 commit
  9. 21 Apr, 2012 1 commit
    • Simon Glass's avatar
      Add 'patman' patch generation, checking and submission script · 0d24de9d
      Simon Glass authored
      What is this?
      
      =============
      
      This tool is a Python script which:
      - Creates patch directly from your branch
      - Cleans them up by removing unwanted tags
      - Inserts a cover letter with change lists
      - Runs the patches through checkpatch.pl and its own checks
      - Optionally emails them out to selected people
      
      It is intended to automate patch creation and make it a less
      error-prone process. It is useful for U-Boot and Linux work so far,
      since it uses the checkpatch.pl script.
      
      It is configured almost entirely by tags it finds in your commits.
      This means that you can work on a number of different branches at
      once, and keep the settings with each branch rather than having to
      git format-patch, git send-email, etc. with the correct parameters
      each time. So for example if you put:
      
      in one of your commits, the series will be sent there.
      
      See the README file for full details.
      END
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      0d24de9d