X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=dgit.git;a=blobdiff_plain;f=dgit.1;h=f2821dffd32ba6172bfcc203674065c1ebb29150;hp=0d395ff5d374156d85b80dbdecb6cfb283203a2a;hb=707db15f3bd08766aa8e89a218d32a744f426791;hpb=476be97f847c7dd52a98647ed9f4240791ff380e

diff --git a/dgit.1 b/dgit.1
index 0d395ff5..f2821dff 100644
--- a/dgit.1
+++ b/dgit.1
@@ -73,6 +73,25 @@ for the distro to which
 .I suite
 belongs.
 
+.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.
+The history generated by this feature is not normally suitable
+for merging back into upstreams,
+as it necessarily contains unattractive pseudomerges.
+
 For your convenience, the
 .B vcs-git
 remote will be set up from the package's Vcs-Git field, if there is
@@ -90,6 +109,10 @@ then dgit fetch defaults to
 .IR suite ;
 otherwise it parses debian/changelog and uses the suite specified
 there.
+
+suite may be
+.IR mainsuite \fB,\fR subsuite ...
+as for clone.
 .TP
 \fBdgit pull\fR [\fIsuite\fP]
 Does dgit fetch, and then merges the new head of the remote tracking