When tests invoke dgit, use --dgit= so that subprocesses use our dgit rather than...

[dgit.git] / dgit.1

diff --git a/dgit.1 b/dgit.1
index 1a6945a13204b9441450583854819e76a35e93da..4b27cdab49e5a9ff5295aaec12a913f4ede4573a 100644 (file)
--- a/dgit.1
+++ b/dgit.1
@@ -59,12 +59,18 @@ The suite's git tip is
 left on the local branch
 .BI dgit/ suite
 ready for work, and on the corresponding dgit remote tracking branch.
-Also, the
+The
 .B origin
 remote will be set up to point to the package's dgit-repos tree
 for the distro to which
 .I suite
 belongs.
+
+For your convenience, the
+.B vcs-git
+remote will be set up from the package's Vcs-Git field, if there is
+one - but note that in the general case the history found there may be
+different to or even disjoint from dgit's view.
 .TP
 \fBdgit fetch\fR [\fIsuite\fP]
 Consults the archive and git-repos to update the git view of
@@ -106,6 +112,10 @@ and
 
 Tagging, signing and actually uploading should be left to dgit push.
 .TP
+.B dgit clean
+Cleans the current working tree (according to the --clean= option in
+force).
+.TP
 .B dgit help
 Print a usage summary.
 .TP
@@ -165,7 +175,7 @@ them.
 
 build-host and build\-dir can be passed as separate
 arguments; this is assumed to be the case if the first argument
-contains no : (except perhaps on in [ ], to support IPv6 address
+contains no : (except perhaps one in [ ], to support IPv6 address
 literals).
 
 You will need similar enough versions of dgit on the build-host and