dgit-user(7): Suggest sbuild-debian-developer-setup(1)

[dgit.git] / dgit.1

diff --git a/dgit.1 b/dgit.1
index c5d76884871315a815cfa6f2dd6fbd24de8d8726..6ee22e822082330ad82f2f2d0ac85c27a82881d2 100644 (file)
--- a/dgit.1
+++ b/dgit.1
@@ -118,6 +118,10 @@ that the generated source package corresponds to the relevant git
 commit.
 
 Tagging, signing and actually uploading should be left to dgit push.
+
+dgit's build operations access the the network,
+to get the -v option right.
+See -v, below.
 .TP
 \fBdgit build-source\fR ...
 Builds the source package, and a changes file for a prospective
@@ -485,7 +489,7 @@ push will still ensure that the .dsc you upload and the git tree
 you push are identical, so this option won't make broken pushes.)
 .TP
 .BR --overwrite [=\fIprevious-version\fR]
-Declare that even though your git branch is not a descendant
+Declare that even though your git branch may not be a descendant
 of the version in the archive
 according to the revision history,
 it really does contain
@@ -506,7 +510,7 @@ changes unless someone committed to git a finalised changelog
 entry, and then made later changes to that version.)
 
 dgit push --overwrite
-will make a
+will, if necessary, make a
 pseudo-merge (that is, something that looks like the result
 of git merge -s ours) to stitch the archive's version into your own
 git history, so that your push is a fast forward from the archive.