The following commit has been merged in the master branch:
commit 4d719ce10fcbdcc29bcc3d5de0ab6ff27e5d1d7b
Author: James Vega <[email protected]>
Date: Fri Feb 18 22:12:58 2011 -0500
bts: Document whitespace is required around the dot/comma separating
command stanzas.
Closes: #595893
Signed-off-by: James Vega <[email protected]>
diff --git a/debian/changelog b/debian/changelog
index ae32a4d..f4e64cd 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -5,8 +5,11 @@ devscripts (2.10.71) UNRELEASED; urgency=low
with --release, otherwise it is not possible to tag after the final build.
[ James Vega ]
- * bts: Use Pod::Text to remove POD markup before displaying the help.
- (Closes: #613502)
+ * bts:
+ + Use Pod::Text to remove POD markup before displaying the help. (Closes:
+ #613502)
+ + Document that whitespace is required around the dot/comma separating
+ command stanzas. (Closes: #595893)
* dget: Ignore IO::File errors from local cache when a URL is given.
The local cache should be used when accessible, but not prevent downloads
when it isn't. (Closes: #599354)
diff --git a/scripts/bts.pl b/scripts/bts.pl
index 26477ab..6e0f896 100755
--- a/scripts/bts.pl
+++ b/scripts/bts.pl
@@ -203,8 +203,9 @@ severity #85942 normal" will not be treated as a comment!)
You can specify multiple commands by separating them with a single dot,
rather like B<update-rc.d>; a single comma may also be used; all the
-commands will then be sent in a single mail. For example (quoting where
-necessary so that B<bts> sees the comment):
+commands will then be sent in a single mail. It is important the dot/comma is
+surrounded by whitespace so it is not mistaken for part of a command. For
+example (quoting where necessary so that B<bts> sees the comment):
% bts severity 95672 normal , merge 95672 95673 \#they are the same!
--
Git repository for devscripts
--
To unsubscribe, send mail to [email protected].
