u-boot.git/tools/patman, branch v2012.10

patman: Use reverse order for changelog

2012-09-26T18:08:32+00:00

Specially when many revisions are need for a patchset, the most
interesting information is about the last set of changes so we output
the changelog in reverse order to easy identification of most recent
change set.

Signed-off-by: Otavio Salvador 
Acked-by: Simon Glass

patman: Do not Cc addresses included in To list

2012-09-02T14:27:07+00:00

In case an address is listed in the To list, those will be skipped on
Cc list or user might end with a duplicated message.

This fixes the case when a tag points to same address used as series
destination thus avoiding duplicated sending.

Signed-off-by: Otavio Salvador

patman: Allow for changelog use in first version of a series

2012-09-02T14:25:33+00:00

When a patchset had a RFC series, a v1 might have a changelog of
changes done since the RFC. The patch changes the range checked for
changelog and allow it to start for version 1.

Signed-off-by: Otavio Salvador 
Acked-by: Simon Glass

patman: don't mess with signoffs

2012-09-02T14:24:51+00:00

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: Ilya Yanok

patman: don't mess with changelog

2012-09-02T14:24:07+00:00

Don't try to sort and uniq changelog entries as this breaks
multiline entries. It will be better to add some real multi-line
support but for now just preserve the entries as is.

Signed-off-by: Ilya Yanok

patman: don't pick changes while processing patches

2012-09-02T14:23:33+00:00

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: Ilya Yanok

patman: fix end of changes detection

2012-09-02T14:22:49+00:00

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: Ilya Yanok

patman: Handle creation of patman config file

2012-06-19T20:51:55+00:00

patman shouts when it couldn't find a $(HOME)/.patman file.
Handle it in a sane way by creating a new one for the user.
It looks for a user.name and user.email in the global .gitconfig
file, waits for the user input if it can't find there. Update the
same in the README

Signed-off-by: Vikram Narayanan 
Acked-by: Simon Glass 
Cc: Simon Glass 
Cc: Wolfgang Denk

patman: Change the location of patman config file

2012-06-19T20:51:36+00:00

Move the config file from ~/.config/patman to ~/.patman as it is
more appropriate to have it there. Update the same in the README.

Signed-off-by: Vikram Narayanan 
Cc: Simon Glass 
Cc: Wolfgang Denk 
Acked-by: Simon Glass

patman: Change the location of patman path

2012-04-30T07:57:48+00:00

Fix the location of patman path in README

Signed-off-by: Vikram Narayanan 
Cc: Simon Glass