do not clean after all

[dgit.git] / dgit.1

diff --git a/dgit.1 b/dgit.1
index ad4be5f0e275f56753b028128ed6837a0c48e31b..37601e765b54446594a18ffe6c758f4fd8bf724d 100644 (file)
--- 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" .
+archive.
 .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
@@ -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
-.TP
-.BI --clean-command= "cmd arg arg"
-dgit push needs to clean the tree to make sure the 
 .SH CONFIGURATION
 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