--clean=git and --clean=none cause dgit to pass -nc to dpkg-buildpackage, suppressing...

[dgit.git] / dgit.1

diff --git a/dgit.1 b/dgit.1
index a33dcb7ef6ba0740e6ad7d3d24ddabf2765a27f5..f183e8e56df58f81ed9ba70c69c2b22200e71631 100644 (file)
--- a/dgit.1
+++ b/dgit.1
@@ -248,11 +248,20 @@ Valid with dgit fetch and dgit pull, only.
 The source tree should be cleaned, before building a source package
 with one of the build options, using
 .BR "git clean -xdf" .
 The source tree should be cleaned, before building a source package
 with one of the build options, using
 .BR "git clean -xdf" .

-This will delete all files which are not tracked by git.
+This will delete all files which are not tracked by git.  Also, -wg
+causes dgit to pass
+.B -nc
+to dpkg-buildpackage, which prevents the package's own clean target
+from being run.
+
+--clean=git is useful when the package's clean target is troublesome;
+the downside is simply that git clean may delete files you forgot to
+git add.

 .TP
 .BR --clean=none | -wn
 Do not clean the tree before building a source package.  If there are
 .TP
 .BR --clean=none | -wn
 Do not clean the tree before building a source package.  If there are

-files which are not in git, a subsequent dgit push will fail.
+files which are not in git, or if the build creates such files, a
+subsequent dgit push will fail.

 .TP
 .BR --clean=dpkg-source | -wd
 Use dpkg-buildpackage to do the clean, so that the source package
 .TP
 .BR --clean=dpkg-source | -wd
 Use dpkg-buildpackage to do the clean, so that the source package


@@ -596,6 +605,10 @@ directory, as with a traditional (non-gitish) dpkg-source workflow.
 You need to retain these tarballs in the parent directory for dgit
 build and dgit push.
 
 You need to retain these tarballs in the parent directory for dgit
 build and dgit push.
 

+dgit repositories could be cloned with standard (git) methods. The
+only exception is that for sourcefull builds / uploads the orig
+tarball(s) need to be present in the parent directory.
+

 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.
 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.