Qualify to Debian the manpage comment about how to do NMU.

[dgit.git] / dgit.1

diff --git a/dgit.1 b/dgit.1
index 90ed69eb9163a42778ff7a64a52d7e6d2fece4b7..8ddab7a74211295603af73b5c78dc30930ecf0b3 100644 (file)
--- a/dgit.1
+++ b/dgit.1
@@ -530,12 +530,14 @@ It is always possible with dgit to clone or fetch a package, make
 changes in git (using git-commit) on the suite branch
 .RB ( "git checkout dgit/" \fIsuite\fR)
 and then dgit push.  You can use whatever gitish techniques you like
-to construct the commit to push; the only requirement is that it is a
+to construct the commits to push;
+the only requirement is that what you push is a
 descendant of the state of the archive, as provided by dgit in the
 remote tracking branch
 .BR remotes/dgit/dgit/ \fIsuite\fR.
 
-If you are using dgit to do an NMU, and don't know about the
+If you are using dgit to do an NMU (in Debian),
+and don't know about the
 maintainers' preferred packaging workflows, you should make your
 changes as a linear series of (logicially separated) commits on top of
 what's already in the archive.