| Submitter | Vikram Narayanan |
|---|---|
| Date | April 27, 2012, 4:39 p.m. |
| Message ID | <4F9ACBC3.20707@gmail.com> |
| Download | mbox | patch |
| Permalink | /patch/155545/ |
| State | Accepted |
| Commit | 330a091c11d48539cc5cbaab708514fe7b386f8c |
| Headers | show |
Comments
Dear Vikram Narayanan, In message <4F9ACBC3.20707@gmail.com> you wrote: > Fix the location of patman path in README > > Signed-off-by: Vikram Narayanan <vikram186@gmail.com> > Cc: Simon Glass <sjg@chromium.org> > --- > tools/patman/README | 6 +++--- > 1 files changed, 3 insertions(+), 3 deletions(-) Applied, thanks. Best regards, Wolfgang Denk
Patch
diff --git a/tools/patman/README b/tools/patman/README index d98f081..4913510 100644 --- a/tools/patman/README +++ b/tools/patman/README @@ -93,17 +93,17 @@ How to run it First do a dry run: -$ ./tools/scripts/patman/patman -n +$ ./tools/patman/patman -n If it can't detect the upstream branch, try telling it how many patches there are in your series: -$ ./tools/scripts/patman/patman -n -c5 +$ ./tools/patman/patman -n -c5 This will create patch files in your current directory and tell you who it is thinking of sending them to. Take a look at the patch files. -$ ./tools/scripts/patman/patman -n -c5 -s1 +$ ./tools/patman/patman -n -c5 -s1 Similar to the above, but skip the first commit and take the next 5. This is useful if your top commit is for setting up testing.
Fix the location of patman path in README Signed-off-by: Vikram Narayanan <vikram186@gmail.com> Cc: Simon Glass <sjg@chromium.org> --- tools/patman/README | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-)