|author||Ian Jackson <email@example.com>||2013-10-25 10:32:17 +0100|
|committer||Ian Jackson <firstname.lastname@example.org>||2013-10-25 10:32:17 +0100|
Clarify the manpage's comments about orig tarballs. Closes: #723605.
2 files changed, 6 insertions, 4 deletions
diff --git a/debian/changelog b/debian/changelog
index 7acc8ed..ad20088 100644
@@ -5,6 +5,7 @@ dgit (0.17~experimental4) experimental; urgency=low
* When using sbuild, pass the arguments to mergechanges in the right
order so that we use the correct Description (the _source one,
not the one from sbuild which didn't get e.g. -v<version>).
+ * Clarify the manpage's comments about orig tarballs. Closes: #723605.
@@ -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