path: root/dgit.1
diff options
authorIan Jackson <>2016-11-07 02:41:44 +0000
committerIan Jackson <>2016-11-07 03:00:33 +0000
commit57c7a33b3b21cd1840e33be2f159c4b7cd5ccf39 (patch)
tree94b1d6db09c521b2e62501d88d90cc4dcfa05c66 /dgit.1
parent9f4e6d4971ba3f1fa8b740df7c400fa3a45fc875 (diff)
Document multisuite
Signed-off-by: Ian Jackson <>
Diffstat (limited to 'dgit.1')
1 files changed, 20 insertions, 0 deletions
diff --git a/dgit.1 b/dgit.1
index 0d395ff..677a51b 100644
--- a/dgit.1
+++ b/dgit.1
@@ -73,6 +73,22 @@ for the distro to which
.I suite
+.I suite
+may be
+.IR mainsuite \fB,\fR subsuite ...
+in which case dgit will synthesize a view giving the most
+recent version in any of the specified suites.
+(The subsuites do not need to have the package.)
+If a subsuite starts with
+.B -
+then mainsuite is prepended.
+Each of the suite names will be individually canonicalised
+to calculate the canonical branch names to use.
+When using this facility, it is important to always specify the
+same suites in the same order:
+dgit will not be make a coherent fast-forwarding history
+view otherwise.
For your convenience, the
.B vcs-git
remote will be set up from the package's Vcs-Git field, if there is
@@ -90,6 +106,10 @@ then dgit fetch defaults to
.IR suite ;
otherwise it parses debian/changelog and uses the suite specified
+suite may be
+.IR mainsuite \fB,\fR subsuite ...
+as for clone.
\fBdgit pull\fR [\fIsuite\fP]
Does dgit fetch, and then merges the new head of the remote tracking