path: root/dgit.1
diff options
authorIan Jackson <>2013-09-26 01:14:55 +0100
committerIan Jackson <>2013-09-26 01:14:55 +0100
commit6c9c982217c2e5fd2f64fa55aaf8a3b6ac89e14f (patch)
treea52a2fd311df10897b76e3f3166d7abaae4de40a /dgit.1
parent68dadfa3503db1f12b4402bbf043d51441a9a412 (diff)
push actually takes an optional suite, like it says in the synopsis.
Diffstat (limited to 'dgit.1')
1 files changed, 3 insertions, 2 deletions
diff --git a/dgit.1 b/dgit.1
index 251af59..b3f8f95 100644
--- a/dgit.1
+++ b/dgit.1
@@ -125,7 +125,7 @@ will be passed on to git-buildpackage.
Tagging, signing and actually uploading should be left to dgit push.
-.B dgit push
+\fBdgit push\fR [\fIsuite\fP]
Does an `upload', pushing the current HEAD to the archive (as a source
package) and to dgit-repos (as git commits). The package must already
have been built ready for upload, with the .dsc and .changes
@@ -139,7 +139,8 @@ signed tag, and finally uses dput to upload the .changes to the
dgit push always uses the package, suite and version specified in the
-debian/changelog and the .dsc, which must agree.
+debian/changelog and the .dsc, which must agree. If the command line
+specifies a suite then that must match too.
If dgit push fails while uploading, it is fine to simply retry the
dput on the .changes file at your leisure.