X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=dgit.1;h=260b742d8421efbd92c91ba7e2b08e63c64ce588;hb=d0c5d6629f42b2efa52fb48a5f24407ef18f86b2;hp=b027db7d8bf37fb268cdb1c9df9b2857d49559b7;hpb=efba7aabcf8f5b83a35eec3c5b11b9eb4a70baf3;p=dgit.git

diff --git a/dgit.1 b/dgit.1
index b027db7d..260b742d 100644
--- a/dgit.1
+++ b/dgit.1
@@ -143,7 +143,10 @@ Tagging, signing and actually uploading should be left to dgit push.
 Does an `upload', pushing the current HEAD to the archive (as a source
 package) and to dgit-repos (as git commits).  The package must already
 have been built ready for upload, with the .dsc and .changes
-left in the parent directory.
+left in the parent directory.  It is normally best to do the build
+with dgit too (eg with dgit sbuild): some existing build tools pass
+unhelpful options to dpkg-source et al by default, which can result in
+the built source package not being identical to the git tree.
 
 In more detail: dgit push checks that the current HEAD corresponds to
 the .dsc.  It then pushes the HEAD to the suite's dgit-repos branch,
@@ -276,7 +279,7 @@ because the dgit git tree does not have a
 .B .pc
 directory.)
 .TP
-.BR --no-quilt-fixup
+.BR --quilt=nocheck | --no-quilt-fixup
 Do not check whether up source format `3.0 (quilt)' metadata needs
 fixing up.  If you use this option and the metadata did in fact need
 fixing up, dgit push will fail.