Patchwork [U-Boot,3/4] patman: Change the location of patman path in README

login
register
mail settings
Submitter Vikram Narayanan
Date April 25, 2012, 3:45 p.m.
Message ID <4F981C1E.3000302@gmail.com>
Download mbox | patch
Permalink /patch/155008/
State Superseded, archived
Delegated to: Anatolij Gustschin
Headers show

Comments

Vikram Narayanan - April 25, 2012, 3:45 p.m.
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(-)
Simon Glass - April 26, 2012, 6:05 p.m.
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

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.