In manpage, do not seem to imply that NMU should be of only one new commit.

diff --git a/debian/changelog b/debian/changelog
index 907635974cd271460c8b446124722db8ce42125b..00e618fa64fc1cd422d26a107d63c457e66b072d 100644 (file)
--- a/debian/changelog
+++ b/debian/changelog
@@ -11,6 +11,8 @@ dgit (1.1) unstable; urgency=low
   * Improve manpage comment about defining a new distro.
   * Document that --quilt=linear is the default for Debian.
   * Fix a formatting problem in --build-products-dir= doc.
+  * In manpage, do not seem to imply that NMU should be of only one
+    new commit.
 
  --
 

diff --git a/dgit.1 b/dgit.1
index 90ed69eb9163a42778ff7a64a52d7e6d2fece4b7..fc883f21b94a74cbc9281867b83db71f4699b1ba 100644 (file)
--- a/dgit.1
+++ b/dgit.1
@@ -530,7 +530,8 @@ 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.