u-boot.git/tools/patman, branch v2013.01

patman: Issue empty change logs for unchanged patches

2012-11-14T09:22:47+00:00

Often a particular patch may change only for some versions of a series.
For versions where there is no change, issue a change log indicating
that (for example 'Changes in v4: None').

For such lines, don't add a blank line afterwards, to conserve space.
Use list.insert() instead of list = [item] + list.

Signed-off-by: Simon Glass 
Tested-by: Stefan Roese

patman: Add additional tags to ignore

2012-11-04T18:00:38+00:00

The BRANCH= tag can be used to indicate the destination branch for a
commit. Ignore this tag.

Also ignore the gerrit 'Commit-Ready:' tag.

Signed-off-by: Simon Glass

patman: force git log commands to not use color

2012-10-19T22:25:46+00:00

Colored logs confuse patman when analyzing logs.
Add --no-color option in git log commands in case
the default config has color.

Signed-off-by: Albert ARIBAUD 
Acked-by: Simon Glass 
Signed-off-by: Tom Rini

patman: Handle checkpatch.pl not providing file/line info

2012-10-15T18:54:04+00:00

Sometimes we don't get a valid filename or line number from checkpatch.pl,
for example if the patch is in a bad format. Deal with this by using a
default value, rather than a stack trace.

Signed-off-by: Simon Glass

patman: Support Series-name tag to name a series

2012-10-15T18:54:03+00:00

Sometimes it is possible to forget the name of the branch you used to
generate an upstream series. To assist with this, add an optional
patman does not use this.

Signed-off-by: Simon Glass

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