X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=dgit.git;a=blobdiff_plain;f=dgit.1;h=49ed4f8b1c99e91e68f66bbf242475be53d20293;hp=f97e458fb0b15fe75cffabd64bed9c7812fe46d7;hb=26827f6e6dfdc5188991059a236f522cf8a696d1;hpb=7de1cca83307cda0d0bf04f8646e23da334f19ef

diff --git a/dgit.1 b/dgit.1
index f97e458f..49ed4f8b 100644
--- a/dgit.1
+++ b/dgit.1
@@ -232,7 +232,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-Dgit-Master
+.B Dgit
 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.
@@ -501,7 +501,7 @@ 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-Dgit-Master
+Debian Policy needs to be updated to describe the new Dgit .dsc
 field (and to specify that it is an RC bug for that field to refer
 to an unavailable commit).
 
@@ -565,5 +565,6 @@ 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.)
+--dry-run does not always work properly, as not doing some of the git
+fetches may result in subsequent actions being different.  Doing a
+non-dry-run dgit fetch first will help.