Author: jamessan
Date: 2009-07-29 17:12:57 +0000 (Wed, 29 Jul 2009)
New Revision: 1952

Modified:
   trunk/debian/changelog
   trunk/scripts/debchange.1
   trunk/scripts/debchange.pl
Log:
debchange: Clarify the wording for the explanation of --force-save-on-release.  
(Closes: #539155)

Modified: trunk/debian/changelog
===================================================================
--- trunk/debian/changelog      2009-07-29 17:04:53 UTC (rev 1951)
+++ trunk/debian/changelog      2009-07-29 17:12:57 UTC (rev 1952)
@@ -1,8 +1,9 @@
-devscripts (2.10.54) unstable; urgency=low
+devscripts (2.10.54) UNRELEASED; urgency=low
 
-  * NOT RELEASED YET
+  * debchange: Clarify the wording for the explanation of
+    --force-save-on-release.  (Closes: #539155)
 
- -- Adam D. Barratt <[email protected]>  Wed, 29 Jul 2009 16:01:54 +0100
+ -- James Vega <[email protected]>  Wed, 29 Jul 2009 19:04:12 +0200
 
 devscripts (2.10.53) unstable; urgency=low
 

Modified: trunk/scripts/debchange.1
===================================================================
--- trunk/scripts/debchange.1   2009-07-29 17:04:53 UTC (rev 1951)
+++ trunk/scripts/debchange.1   2009-07-29 17:12:57 UTC (rev 1952)
@@ -174,8 +174,8 @@
 .TP
 .BR \-\-force\-save\-on\-release
 When \-\-release is used and an editor opened to allow inspection
-of the changelog, force the file to be saved in the editor even
-if no further changes are made. (default)
+of the changelog, require the user to save the changelog their editor opened.
+Otherwise, the original changelog will not be modified. (default)
 .TP
 .BR \-\-no\-force\-save\-on\-release
 Do not do so. Note that a dummy changelog entry made be supplied

Modified: trunk/scripts/debchange.pl
===================================================================
--- trunk/scripts/debchange.pl  2009-07-29 17:04:53 UTC (rev 1951)
+++ trunk/scripts/debchange.pl  2009-07-29 17:12:57 UTC (rev 1952)
@@ -89,8 +89,9 @@
          specified by --distribution).
   --force-save-on-release
          When --release is used and an editor opened to allow inspection
-         of the changelog, force the file to be saved in the editor even
-         if no further changes are made. (default)
+         of the changelog, require the user to save the changelog their
+         editor opened.  Otherwise, the original changelog will not be
+         modified. (default)
   --no-force-save-on-release
          Do not do so. Note that a dummy changelog entry made be supplied
          in order to achieve the same effect - e.g. $progname --release ""



-- 
To unsubscribe, send mail to [email protected].

Reply via email to