1. 04 Apr, 2013 2 commits
  2. 04 Nov, 2012 1 commit
  3. 19 Oct, 2012 1 commit
  4. 02 Sep, 2012 3 commits
    • Ilya Yanok's avatar
      patman: don't mess with signoffs · c7379149
      Ilya Yanok authored
      
      
      Currently patman assumes that there should be only one Signoff line
      and this is obviously incorrect: we often have to work with patches
      containing other people signoffs. Moreover, it's really desirable
      to preserve the comments between signoffs.
      
      So until some sophisticated signoff processing will be developed I
      suggest just don't mess with signoffs at all and treat them like
      plain text lines. The only drawback I've found so far is the case
      where you have a patch with someones else signoff but not yours and
      also have to patman tags under signoff line. In this case you will
      get extra empty line between signoffs.
      Signed-off-by: default avatarIlya Yanok <ilya.yanok@cogentembedded.com>
      c7379149
    • Ilya Yanok's avatar
      patman: don't pick changes while processing patches · a8840cb2
      Ilya Yanok authored
      
      
      We already got all changes from git log output and the comment
      to the ProcessLine function clearly states that 'patch' mode
      is not for scanning tags.
      Signed-off-by: default avatarIlya Yanok <ilya.yanok@cogentembedded.com>
      a8840cb2
    • Ilya Yanok's avatar
      patman: fix end of changes detection · 05e5b735
      Ilya Yanok authored
      
      
      Changes may end in '---' line or Signoff line (generated by
      git format-patch) in case of Series-changes: lines being
      the last ones in commit message. So detect it properly.
      Signed-off-by: default avatarIlya Yanok <ilya.yanok@cogentembedded.com>
      05e5b735
  5. 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