* [U-Boot] [PATCH 3/4] patman: Change the location of patman path in README
@ 2012-04-25 15:45 Vikram Narayanan
2012-04-26 18:05 ` Simon Glass
0 siblings, 1 reply; 2+ messages in thread
From: Vikram Narayanan @ 2012-04-25 15:45 UTC (permalink / raw)
To: u-boot
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(-)
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.
--
1.7.4.1
^ permalink raw reply related [flat|nested] 2+ messages in thread
* [U-Boot] [PATCH 3/4] patman: Change the location of patman path in README
2012-04-25 15:45 [U-Boot] [PATCH 3/4] patman: Change the location of patman path in README Vikram Narayanan
@ 2012-04-26 18:05 ` Simon Glass
0 siblings, 0 replies; 2+ messages in thread
From: Simon Glass @ 2012-04-26 18:05 UTC (permalink / raw)
To: u-boot
Hi Vikram,
On Thu, Apr 26, 2012 at 3:45 AM, Vikram Narayanan <vikram186@gmail.com>wrote:
> 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(-)
>
> 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:
>
The version of this that I picked up from patchwork has a space at the
start of the above two lines, so needs --ignore-whitespace to apply. Can
you please check this?
>
> -$ ./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.
> --
> 1.7.4.1
>
> Regards,
Simon
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2012-04-26 18:05 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-04-25 15:45 [U-Boot] [PATCH 3/4] patman: Change the location of patman path in README Vikram Narayanan
2012-04-26 18:05 ` Simon Glass
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox