summaryrefslogtreecommitdiff
path: root/dgit.1
diff options
context:
space:
mode:
authorIan Jackson <ijackson@chiark.greenend.org.uk>2015-07-20 13:34:30 +0100
committerIan Jackson <ijackson@chiark.greenend.org.uk>2015-07-20 13:34:30 +0100
commit878762dc1c47ef2f417b4ccde514b9b811c15dc3 (patch)
treefe9f6518681f7cd17417e17c07733ce736a208d0 /dgit.1
parent5cbfd93057610740cf7954ce3d29a2d14bacd603 (diff)
In manpage, do not seem to imply that NMU should be of only one new commit.
Diffstat (limited to 'dgit.1')
-rw-r--r--dgit.13
1 files changed, 2 insertions, 1 deletions
diff --git a/dgit.1 b/dgit.1
index 90ed69e..fc883f2 100644
--- 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.