path: root/dgit.1
diff options
authorIan Jackson <>2013-08-17 17:12:03 +0100
committerIan Jackson <>2013-08-17 17:12:03 +0100
commitf5bb5d94a3c7d661b7f0253969e1490ffc994490 (patch)
treea673fb4b5c6f076d186ec44eb7deaba2cffabc4c /dgit.1
parentc49ed487a8eba41e990e483dc1851c817ed5237a (diff)
do not clean after all
Diffstat (limited to 'dgit.1')
1 files changed, 1 insertions, 5 deletions
diff --git a/dgit.1 b/dgit.1
index ad4be5f..37601e7 100644
--- a/dgit.1
+++ b/dgit.1
@@ -52,8 +52,7 @@ Tagging and signing should be left to dgit push.
does an `upload', pushing the current HEAD to the archive (as a source
package) and to dgit-repos (as git commits). This also involves
making a signed git tag, and signing the files to be uploaded to the
-archive. dgit push does a
-.BR "debian/rules clean" .
It is always possible with dgit to clone or fetch a package, make
changes in git (using git-commit) on the suite branch
@@ -233,9 +232,6 @@ there is no way to ask the archive to do this without knowing the
name of an existing package. Without --new we can just use the
package we are trying to push. But with --new that will not work, so
we guess that
-.BI --clean-command= "cmd arg arg"
-dgit push needs to clean the tree to make sure the
dgit looks at the following git config keys to control its behaviour.
You may set them with git-config (either in system-global or per-tree