23 Mar, 2014
1 commit
-
Add a new Patch-cc: tag which performs the service now provided by
the Cc: tag. The Cc: tag is interpreted by git send-email but
ignored by patman.So now:
Cc: patman does nothing. (git send-email can cc patches)
Patch-cc: patman Cc's patch and removes this tag from the patchSigned-off-by: Simon Glass
22 Nov, 2013
1 commit
-
Sometimes a commit should have notes enclosed with it rather
than withing the cover letter -- possibly even because there
is no cover letter. Add a 'Commit-notes' tag, similar to the
'Series-notes' one; lines between this tag and the next END
line are inserted in the patch right after the '---' commit
delimiter.Change-Id: I01e99ae125607dc6dec08f3be8a5a0b37f0a483d
Signed-off-by: Albert ARIBAUD
Signed-off-by: Simon Glass
(Updated README)
24 Jul, 2013
1 commit
-
Signed-off-by: Wolfgang Denk
[trini: Fixup common/cmd_io.c]
Signed-off-by: Tom Rini
16 Jul, 2013
1 commit
-
adjust instructions for the invocation of Patman's self test: the -t
flag appears to have a different meaning now, refer to the --test option
for the builtin unit test; adjust a directory location and make sure to
run the file which resides in the source directorySigned-off-by: Gerhard Sittig
Acked-by: Simon Glass
09 Apr, 2013
1 commit
-
For some series with lots of changes it is annoying that duplicate change
log items are not caught. It is also helpful sometimes to sort the change
logs.Add a Series-process-log tag to enable this, which can be placed in a
commit to control this.The change to the Cc: line is to fix a checkpatch warning.
Signed-off-by: Simon Glass
Reviewed-by: Doug Anderson
05 Apr, 2013
3 commits
-
A few of the help messages are not quite right, and there is a typo
in the README. Fix these.Signed-off-by: Simon Glass
Reviewed-by: Doug Anderson -
The cover letter is sent to everyone who is on the Cc list for any of
the patches in the series. Sometimes it is useful to send just the cover
letter to additional people, so that they are aware of the series, but
don't need to wade through all the individual patches.Add a new Cover-letter-cc tag for this purpose.
Signed-off-by: Simon Glass
Reviewed-by: Doug Anderson -
Although "Reviewed-by:" is a tag that gerrit adds, it's also a tag
used by upstream. Stripping it is undesirable. In fact, we should
treat it as important.Signed-off-by: Doug Anderson
Reviewed-by: Otavio Salvador
Acked-by: Simon Glass
01 Feb, 2013
4 commits
-
There are cases that we want to support different settings (or maybe
even different aliases) for different projects. Add support for this
by:
* Adding detection for two big projects: U-Boot and Linux.
* Adding default settings for Linux (U-Boot is already good with the
standard patman defaults).
* Extend the new "settings" feature in .patman to specify per-project
settings.Signed-off-by: Doug Anderson
Acked-by: Simon Glass -
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:[settings]
ignore_errors: True
process_tags: False
verbose: TrueThe settings functionality is also used in a future change which adds
support for per-project settings.Signed-off-by: Doug Anderson
-
For Linux the best way to figure out where to send a patch is with the
"get_maintainer.pl" script. Add support for calling it from patman.
Support is added unconditionally for "scripts/get_maintainer.pl" in
case it is helpful for any other projects.Signed-off-by: Doug Anderson
-
If we're sending a cover letter make sure to CC everyone that we're
CCing on each of the individual patches.Signed-off-by: Doug Anderson
16 Oct, 2012
1 commit
-
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
20 Jun, 2012
2 commits
-
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 READMESigned-off-by: Vikram Narayanan
Acked-by: Simon Glass
Cc: Simon Glass
Cc: Wolfgang Denk -
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
30 Apr, 2012
2 commits
-
Fix the location of patman path in README
Signed-off-by: Vikram Narayanan
Cc: Simon Glass -
Signed-off-by: Vikram Narayanan
Cc: Simon Glass
Acked-by: Simon Glass
22 Apr, 2012
1 commit
-
Also tiny style cleanup to tools/patman/README
Signed-off-by: Wolfgang Denk
21 Apr, 2012
1 commit
-
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 peopleIt 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.
ENDSigned-off-by: Simon Glass