.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
.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
.BR sbuild ,
.BR ssh ,
.BR dgit ,
+.BR apt-get ,
+.BR apt-cache ,
.BR gbp-pq ,
.BR gbp-build ,
or
.BR gpg ,
.BR ssh ,
.BR dgit ,
+.BR apt-get ,
+.BR apt-cache ,
.BR git ,
.BR gbp-pq ,
.BR gbp-build ,