Do not remove destination when clone fails because it already exists (!)

[dgit.git] / dgit.1

diff --git a/dgit.1 b/dgit.1
index 8b1c7f9c9367898c59e74ef2245a1feeaa348fa8..6449ea34df2b19f983d9fcfa2c1d81d9dabc38b7 100644 (file)
--- a/dgit.1
+++ b/dgit.1
@@ -169,7 +169,8 @@ contains no : (except perhaps on in [ ], to support IPv6 address
 literals).
 
 You will need similar enough versions of dgit on the build-host and
-the invocation host.
+the invocation host.  The build-host needs gnupg installed, with your
+public key in its keyring (but not your private key, obviously).
 .TP
 .B dgit quilt-fixup
 Looks to see if the tree is one which dpkg-source cannot properly
@@ -398,6 +399,9 @@ instead.  Furthermore, the specified directory will be emptied,
 removed and recreated before dgit starts, rather than removed
 after dgit finishes.  The directory specified must be an absolute
 pathname.
+.TP
+.BI --no-rm-on-error
+Do not delete the destination directory if clone fails.
 .SH WORKFLOW - SIMPLE
 It is always possible with dgit to clone or fetch a package, make
 changes in git (using git-commit) on the suite branch
@@ -508,6 +512,10 @@ build and dgit push.
 To a user looking at the archive, changes pushed using dgit look like
 changes made in an NMU: in a `3.0 (quilt)' package the delta from the
 previous upload is recorded in a new patch constructed by dpkg-source.
+.SH READ-ONLY DISTROS
+Distros which do not maintain a set of dgit history git repositories
+can still be used in a read-only mode with dgit.  Currently Ubuntu
+is configured this way.
 .SH PACKAGE SOURCE FORMATS
 If you are not the maintainer, you do not need to worry about the
 source format of the package.  You can just make changes as you like