telnet_server: drop unused options

[fw/openocd] / doc / manual / release.txt

diff --git a/doc/manual/release.txt b/doc/manual/release.txt
index 8611bb7b0920531e7cb6ae4daf0e73d151dee857..83f668f5224398f17f727b9c70ad9deb34ba8910 100644 (file)
--- a/doc/manual/release.txt
+++ b/doc/manual/release.txt
@@ -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
@@ -334,7 +334,7 @@ git tag -m "The openocd-${PACKAGE_VERSION} release." "${PACKAGE_TAG}"
      configuring its contents, using them to build a copy of OpenOCD,
      and verifying that the result prints the correct release version
      in its startup banner.  (For example,
-     "configure --enable-ft2232_libftdi --enable-parport"
+     "configure --enable-parport"
      then "make" and run "src/openocd -v" as a sanity check.)
   -# Run <code>make docs</code> to create the
      documentation which will be published.