Dgit.pm: git_cat_file: clarify scalar context semantics

[dgit.git] / dgit-user.7.pod

diff --git a/dgit-user.7.pod b/dgit-user.7.pod
index 95d08d8e6ee2010669775e8e6e1c27777616ec5b..ad0cca1da867e3bd19623f0e942723170136627d 100644 (file)
--- a/dgit-user.7.pod
+++ b/dgit-user.7.pod
@@ -126,7 +126,8 @@ If you don't know what you're running, try this:
 =back
 
 For Debian, you should add C<,-security>
-to the end of the suite name.
+to the end of the suite name,
+unless you're on unstable or testing.
 Hence, in our example
 C<jessie> becomes C<jessie,-security>.
 (Yes, with a comma.)
@@ -148,9 +149,11 @@ This, the I<remote suite branch>,
 is synthesized by your local copy of dgit.
 It is fast forwarding.
 
-Debian separates out the security updates, into C<debian-security>.
-Telling dgit C<debian,-security> means that it should include 
-any updates available in C<debian-security>.
+Debian separates out the security updates, into C<*-security>.
+Telling dgit C<jessie,-security> means that it should include 
+any updates available in C<jessie-security>.
+The comma notation is a request to dgit to track jessie,
+or jessie-security if there is an update for the package there.
 
 (You can also dgit fetch in a tree that wasn't made by dgit clone.
 If there's no C<debian/changelog>