summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorIan Jackson <ijackson@chiark.greenend.org.uk>2016-11-07 02:41:44 +0000
committerIan Jackson <ijackson@chiark.greenend.org.uk>2016-11-07 03:00:33 +0000
commit57c7a33b3b21cd1840e33be2f159c4b7cd5ccf39 (patch)
tree94b1d6db09c521b2e62501d88d90cc4dcfa05c66
parent9f4e6d4971ba3f1fa8b740df7c400fa3a45fc875 (diff)
Document multisuite
Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
-rw-r--r--debian/changelog2
-rw-r--r--dgit-user.7.pod2
-rw-r--r--dgit.120
3 files changed, 23 insertions, 1 deletions
diff --git a/debian/changelog b/debian/changelog
index bdc13ea..32064c1 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -8,6 +8,8 @@ dgit (2.10~) unstable; urgency=medium
the user on the local dgit branch, not on `master'.
* Actually honour the branch name, if we are on dgit branch, to specify
the suite, as documented in the manpage.
+ * New comma-separated multiple-suite merging facility (readonly),
+ so that users can easily track "jessie, or jessie-security".
--
diff --git a/dgit-user.7.pod b/dgit-user.7.pod
index fc0d590..d341605 100644
--- a/dgit-user.7.pod
+++ b/dgit-user.7.pod
@@ -30,7 +30,7 @@ or L<dgit(1)> and L<dgit(7)>.
=over 4
- % dgit clone glibc jessie
+ % dgit clone glibc jessie,-security
% cd glibc
% wget 'https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=28250;mbox=yes;msg=89' | patch -p1 -u
% git commit -a -m 'Fix libc lost output bug'
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
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.
+
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
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