summaryrefslogtreecommitdiff
path: root/tools/patman/README
diff options
context:
space:
mode:
authorVikram Narayanan <vikram186@gmail.com>2012-04-27 06:39:31 +0000
committerWolfgang Denk <wd@denx.de>2012-04-30 09:57:48 +0200
commit330a091c11d48539cc5cbaab708514fe7b386f8c (patch)
tree7862869584144ca094bd49cee1fb2b0a299a46c6 /tools/patman/README
parent1713247ffea7c15e4e94c451d609eb52e0c9995b (diff)
downloadu-boot-imx-330a091c11d48539cc5cbaab708514fe7b386f8c.zip
u-boot-imx-330a091c11d48539cc5cbaab708514fe7b386f8c.tar.gz
u-boot-imx-330a091c11d48539cc5cbaab708514fe7b386f8c.tar.bz2
patman: Change the location of patman path
Fix the location of patman path in README Signed-off-by: Vikram Narayanan <vikram186@gmail.com> Cc: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'tools/patman/README')
-rw-r--r--tools/patman/README6
1 files changed, 3 insertions, 3 deletions
diff --git a/tools/patman/README b/tools/patman/README
index d9820ab..7ba9e80 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.