dev-doc: fix to release process docs
authorFreddie Chopin <freddie.chopin@gmail.com>
Sun, 28 Apr 2013 11:33:16 +0000 (13:33 +0200)
committerFreddie Chopin <freddie.chopin@gmail.com>
Thu, 2 May 2013 16:42:26 +0000 (16:42 +0000)
Change-Id: I916e7ff1af211baef1c6d56fd44d292ee6983599
Signed-off-by: Freddie Chopin <freddie.chopin@gmail.com>
Reviewed-on: http://openocd.zylin.com/1368
Tested-by: jenkins
Reviewed-by: Spencer Oliver <spen@spen-soft.co.uk>
doc/manual/release.txt

index 8611bb7b0920531e7cb6ae4daf0e73d151dee857..d1447569204b217380f6432fb79c7e14845500da 100644 (file)
@@ -111,7 +111,7 @@ configure.ac script of a local copy of the source tree, giving
 a version label like <em>0.3.0-foo</em>:
 
 @code
-tools/release/version.sh version tag add foo
+tools/release/version.sh tag add foo
 @endcode
 
 This command will modify the configure.ac script in your working copy
@@ -125,7 +125,7 @@ each time a derived package is released, incrementing the tag's
 version to facilitate tracking the changes you have distributed.
 
 @code
-tools/release/version.sh version bump tag foo
+tools/release/version.sh bump tag foo
 @endcode
 
 Of course, any patches in your branches must be provided to