X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=dgit.git;a=blobdiff_plain;f=dgit.1;h=a226350cf7940b82060b79b19d5d36946ab576a7;hp=50cc3a6f7c4532b60da6a9efe3da340fb808e90b;hb=8b9c62a712a865440b0c56c0d6d45c53d7df1c29;hpb=6162f69f8f3611b2da125a11d5ac24cf11045e96

diff --git a/dgit.1 b/dgit.1
index 50cc3a6f..a226350c 100644
--- a/dgit.1
+++ b/dgit.1
@@ -77,7 +77,7 @@ dgit push can operate on any commit which is a descendant of the
 current dgit/suite tip in dgit-repos.
 
 Uploads made by dgit contain an additional field
-.B Vcs-Git-Master
+.B Vcs-Dgit-Master
 in the source package .dsc.  (This is added by dgit push.)
 This specifies a commit (an ancestor of the dgit/suite
 branch) whose tree is identical to the unpacked source upload.
@@ -166,24 +166,19 @@ on the dgit command line.
 .TP
 .BI dgit-distro. distro .archive-query
 .TP
+.BI dgit-distro. distro .archive-query-default-component
+.TP
 .BI dgit-distro. distro .ssh
 .TP
 .BR dgit.default. *
 for each
 .BR dgit-distro. \fIdistro\fR . *
 .SH BUGS
-dgit will only work with packages in main. The madison http query API
-does not give the component.
-
-dgit assumes knowledge of the archive layout.  There appears to be no
-sane way to find the path in the archive pool of the .dsc for a
-particular suite.
-
 We should be using some kind of vhost/vpath setup for the git repos on
 alioth, so that they can be moved later if and when this turns out to
 be a good idea.
 
-Debian Policy needs to be updated to describe the new Vcs-Git-Master
+Debian Policy needs to be updated to describe the new Vcs-Dgit-Master
 field (and to specify that it is an RC bug for that field to refer
 to an unavailable commit).
 
@@ -221,5 +216,10 @@ line numbers in dgit.
 
 The option parser requires values to be cuddled to the option name.
 
+dgit assumes knowledge of the archive layout.  There appears to be no
+sane way to find the path in the archive pool of the .dsc for a
+particular suite.  I'm assured that the archive layout is a
+`well known algorithm' by now.
+
 --dry-run often does not work with fetch, even though this is a
 logically plausible request.  (It fails, instead.)