path: root/dgit.7
diff options
authorIan Jackson <>2015-07-01 18:33:25 +0100
committerIan Jackson <>2015-07-04 19:24:46 +0100
commit71d71cb4e886f068fe5c6f29f265a4ff47df13d1 (patch)
tree9acecace2e83e528b5104703fe116f80319c2e6b /dgit.7
parentcfd5e47a4a0d485c2cbb93cccad40e8086de52ea (diff)
Manpages: Other clarifications and improvements.
Diffstat (limited to 'dgit.7')
1 files changed, 25 insertions, 3 deletions
diff --git a/dgit.7 b/dgit.7
index a3ea84c..6c74f40 100644
--- a/dgit.7
+++ b/dgit.7
@@ -53,9 +53,9 @@ the dgit/suite branch.
dgit expects repos that it works with to have a
.B dgit
-remote. This refers to the well-known dgit-repos location
-(currently, the dgit-repos project on Alioth). dgit fetch updates
-the remote tracking branch for dgit/suite.
+remote. This refers to the well-known dgit-repos location (on a
+dedicated Debian VM). dgit fetch updates the remote tracking branch
+for dgit/suite.
dgit does not (currently) represent the orig tarball(s) in git. The
orig tarballs are downloaded (by dgit clone) into the parent
@@ -149,5 +149,27 @@ Of course it may also be that the differences are due to build system
bugs, which cause unintended files to end up in the source package.
dgit will notice this and complain. You may have to fix these bugs
before you can unify your existing git history with dgit's.
+A related problem is unexpected behaviour by a package's
+.B clean
+If a package's rules
+remove or modify files which are distributed in the package,
+or simply forgets to remove certain files,
+dgit will complain that the tree is dirty.
+The solution is to use
+.BR "dgit -wg" " aka " "--clean=git" ,
+which instructs dgit to use git clean instead of the package's
+build target,
+along with perhaps
+.B git reset --hard
+before each build.
+This is 100% reliable, but has the downside
+that if you forget to git add or to commit, and then use
+.BR "dgit -wg" " or " "git reset --hard" ,
+your changes may be lost.