10 May, 2014
1 commit
-
This sort of failure is rare, but the code to deal with it is wrong.
Fix it.Signed-off-by: Simon Glass
24 Jul, 2013
1 commit
-
Signed-off-by: Wolfgang Denk
[trini: Fixup common/cmd_io.c]
Signed-off-by: Tom Rini
15 May, 2013
1 commit
-
Rather than a backtrace, produce a nice error message when an invalid
branch is provided to buildman.Signed-off-by: Simon Glass
19 Apr, 2013
1 commit
-
The git config parameter log.decorate is quite useful when working with git.
Patman, however can not handle the decorated output when parsing the commit.
To prevent this use the '--no-decorate' switch for git-log.Signed-off-by: Andreas Bießmann
Acked-by: Simon Glass
09 Apr, 2013
1 commit
-
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: Simon Glass
Reviewed-by: Doug Anderson
05 Apr, 2013
4 commits
-
Some versions of git don't seem to prompt you for the message ID that
your series is in reply to. Allow specifying this from the command
line.Signed-off-by: Doug Anderson
Acked-by: Simon Glass -
Add methods to find out the commits in a branch, clone a repo and
fetch from a repo.Signed-off-by: Simon Glass
-
Make raise_on_error a parameter so that we can control which commands
raise and which do not. If we get an error reading the alias file, just
continue.Signed-off-by: Simon Glass
-
Rather than returning a list of things, return an object. That makes it
easier to access the returned items, and easier to extend the return
value later.Signed-off-by: Simon Glass
01 Feb, 2013
2 commits
-
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
-
Several of the patman doctests assume that patman was run with:
./patmanFix them so that they work even if patman is run with just "patman"
(because patman is in the path).Signed-off-by: Doug Anderson
Acked-by: Simon Glass
20 Oct, 2012
1 commit
-
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
20 Jun, 2012
1 commit
-
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
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