summaryrefslogtreecommitdiff
path: root/dgit.1
diff options
context:
space:
mode:
authorIan Jackson <ijackson@chiark.greenend.org.uk>2013-10-25 10:32:17 +0100
committerIan Jackson <ijackson@chiark.greenend.org.uk>2013-10-25 10:32:17 +0100
commit3223d3f138645887586ad0cb77f28db3b13a0709 (patch)
treea93ad6e07d445d786bed57c6f33bb35581aa62d3 /dgit.1
parent6e24ac7bb85e30df00b3d14853b049e3f06b6dec (diff)
Clarify the manpage's comments about orig tarballs. Closes: #723605.
Diffstat (limited to 'dgit.1')
-rw-r--r--dgit.19
1 files changed, 5 insertions, 4 deletions
diff --git a/dgit.1 b/dgit.1
index c261300..c3caa49 100644
--- a/dgit.1
+++ b/dgit.1
@@ -481,10 +481,11 @@ 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.
-dgit does not (currently) represent the orig tarball(s) in git; nor
-does it represent the patch statck of a `3.0 (quilt)' package. The
-orig tarballs are downloaded and kept in the parent directory, as with
-a traditional (non-gitish) dpkg-source workflow.
+dgit does not (currently) represent the orig tarball(s) in git. The
+orig tarballs are downloaded (by dgit clone) into the parent
+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.
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