summaryrefslogtreecommitdiff
path: root/dgit.1
diff options
context:
space:
mode:
authorIan Jackson <ijackson@chiark.greenend.org.uk>2013-08-17 17:12:32 +0100
committerIan Jackson <ijackson@chiark.greenend.org.uk>2013-08-17 17:12:32 +0100
commit916da427127794108f20f80d5018493002b81876 (patch)
treee3e223b1d447a0a2c3581935034c1f44ec975e9a /dgit.1
parentf5bb5d94a3c7d661b7f0253969e1490ffc994490 (diff)
fix quilt fixup
Diffstat (limited to 'dgit.1')
-rw-r--r--dgit.15
1 files changed, 4 insertions, 1 deletions
diff --git a/dgit.1 b/dgit.1
index 37601e7..8d4d201 100644
--- a/dgit.1
+++ b/dgit.1
@@ -52,7 +52,10 @@ 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.
+archive. (For a format `3.0 (quilt)' source package, dgit push
+may also have to make a commit on your current branch to contain
+quilt metadata. It will do this automatically.)
+.BR "debian/rules clean" .
.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