1. 09 Oct, 2016 1 commit
  2. 19 Sep, 2016 1 commit
  3. 18 Mar, 2016 1 commit
  4. 21 Jan, 2016 1 commit
  5. 09 Sep, 2015 1 commit
    • Masahiro Yamada's avatar
      Revert "patman: use -D option for git format-patch" · 8d3595a4
      Masahiro Yamada authored
      This reverts commit 19b4a336.
      Since that commit, patman generates useless patches for file removal;
      "git format -D" prints only the header but not the diff when deleting
      files, and "git am" always refuses such patches.
      The following is the quotation from "man git-format-patch":
        -D, --irreversible-delete
          Omit the preimage for deletes, i.e. print only the header but
          not the diff between the preimage and /dev/null. The resulting
          patch is not meant to be applied with patch nor git apply; this
          is solely for people who want to just concentrate on reviewing
          the text after the change. In addition, the output obviously
          lack enough information to apply such a patch in reverse, even
          manually, hence the name of the option.
      Signed-off-by: default avatarMasahiro Yamada <yamada.masahiro@socionext.com>
      Acked-by: default avatarSimon Glass <sjg@chromium.org>
  6. 26 Aug, 2015 1 commit
  7. 23 Apr, 2015 1 commit
  8. 15 Feb, 2015 1 commit
  9. 30 Jan, 2015 1 commit
    • Peter Tyser's avatar
      patman: Make dry-run output match real functionality · 2181830f
      Peter Tyser authored
      When run with the --dry-run argument patman prints out information
      showing what it would do.  This information currently doesn't line up
      with what patman/git send-email really do.  Some basic examples:
      - If an email address is addressed via "Series-cc" and "Patch-cc" patman
        shows that email address would be CC-ed two times.
      - If an email address is addressed via "Series-to" and "Patch-cc" patman
        shows that email address would be sent TO and CC-ed.
      - If an email address is addressed from a combination of tag aliases,
        get_maintainer.pl output, "Series-cc", "Patch-cc", etc patman shows
        that the email address would be CC-ed multiple times.
      Patman currently does try to send duplicate emails like the --dry-run
      output shows, but "git send-email" intelligently removes duplicate
      addresses so this patch shouldn't change the non-dry-run functionality.
      Change patman's output and email addressing to line up with the
      "git send-email" logic.  This trims down patman's dry-run output and
      prevents confusion about what patman will do when emails are actually
      Signed-off-by: default avatarPeter Tyser <ptyser@xes-inc.com>
      Acked-by: default avatarSimon Glass <sjg@chromium.org>
      Tested-by: default avatarSimon Glass <sjg@chromium.org>
  10. 15 Jan, 2015 2 commits
  11. 09 Sep, 2014 1 commit
  12. 05 Sep, 2014 4 commits
  13. 28 Aug, 2014 1 commit
  14. 13 Aug, 2014 2 commits
  15. 28 Jul, 2014 1 commit
    • Masahiro Yamada's avatar
      patman: make "No recipient" checking more tolerant · ee860c60
      Masahiro Yamada authored
      If Series-to tag is missing, Patman exits with a message
      "No recipient".
      This is just annoying for those who had already added
      sendemail.to configuration.
      I guess many developers have
                to = u-boot@lists.denx.de
      in their .git/config because the 'To: u-boot@lists.denx.de' field
      should always be added when sending patches.
      That seems more reasonable rather than adding
      'Series-to: u-boot@lists.denx.de' to every patch series.
      Patman should exit only when both Series-to tag and sendemail.to
      configuration are mising.
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      Cc: Simon Glass <sjg@chromium.org>
      Acked-by: default avatarSimon Glass <sjg@chromium.org>
  16. 07 Jul, 2014 1 commit
    • Simon Glass's avatar
      patman: Only apply patches when we know the original HEAD · 4251978a
      Simon Glass authored
      When patman applies the patches it checks out a new branch, uses 'git am'
      to apply the patches one by one, and then tries to go back to the old
      branch. If you try this when the branch is 'undefined', this doesn't work
      as patman cannot restore the correct branch after applying the patches.
      It seems that 'undefined' is created by git and is persistent after it is
      created, so that you can end up on quite an old branch.
      Add a check for the 'undefined' branch to avoid this.
      Reported-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
  17. 09 May, 2014 1 commit
  18. 24 Jul, 2013 1 commit
  19. 14 May, 2013 1 commit
  20. 18 Apr, 2013 1 commit
  21. 08 Apr, 2013 1 commit
    • Simon Glass's avatar
      patman: Provide option to ignore bad aliases · a1318f7c
      Simon Glass authored
      Often it happens that patches include tags which don't have aliases. It
      is annoying that patman fails in this case, and provides no option to
      continue other than adding empty tags to the .patman file.
      Correct this by adding a '-t' option to ignore tags that don't exist.
      Print a warning instead.
      Since running the tests is not a common operation, move this to --test
      instead, to reserve -t for this new option.
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      Reviewed-by: default avatarDoug Anderson <dianders@chromium.org>
  22. 04 Apr, 2013 4 commits
  23. 31 Jan, 2013 2 commits
    • Doug Anderson's avatar
      patman: Add support for settings in .patman · 8568baed
      Doug Anderson authored
      This patch adds support for a [settings] section in the .patman file.
      In this section you can add settings that will affect the default
      values for command-line options.
      Support is added in a generic way such that any setting can be updated
      by just referring to the "dest" of the option that is passed to the
      option parser.  At the moment options that would make sense to put in
      settings are "ignore_errors", "process_tags", and "verbose".  You
      could override them like:
       ignore_errors: True
       process_tags: False
       verbose: True
      The settings functionality is also used in a future change which adds
      support for per-project settings.
      Signed-off-by: default avatarDoug Anderson <dianders@chromium.org>
    • Doug Anderson's avatar
      patman: Allow tests to run even if patman is in the path · a970048e
      Doug Anderson authored
      Several of the patman doctests assume that patman was run with:
      Fix them so that they work even if patman is run with just "patman"
      (because patman is in the path).
      Signed-off-by: default avatarDoug Anderson <dianders@chromium.org>
      Acked-by: default avatarSimon Glass <sjg@chromium.org>
  24. 19 Oct, 2012 1 commit
  25. 19 Jun, 2012 1 commit
  26. 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.
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>