diff options
2 files changed, 10 insertions, 1 deletions
diff --git a/debian/changelog b/debian/changelog
index 7969a61..4f2e64d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -61,7 +61,8 @@ dgit (0.23~) unstable; urgency=low
* Fix inaccurate error message when archive's git hash is not an
ancestor of git repo's git hash.
- * Use ftpmasterapi archive query method. (Closes:#727702.)
+ * Use ftpmasterapi archive query method.
+ (Closes:#727702. Also partly obsoletes #768470.)
* Turn all perl warnings into errors using $SIG{__WARN__}.
@@ -76,6 +77,10 @@ dgit (0.23~) unstable; urgency=low
* Detect and bomb out on vendor-specific `3.0 (quilt)' patch series.
* Provide example workflow for dgit rpush. Closes:#763334.
+ (Also part of the fix for #768470.)
+ * Document that dgit repos are cloneable with git, in dgit(1)
+ section MODEL. [Andreas Barth.] Closes:#768470.
diff --git a/dgit.1 b/dgit.1
index a33dcb7..9705f0a 100644
--- a/dgit.1
+++ b/dgit.1
@@ -596,6 +596,10 @@ 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.
+dgit repositories could be cloned with standard (git) methods. The
+only exception is that for sourcefull builds / uploads the orig
+tarball(s) need to be present in the parent directory.
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
previous upload is recorded in a new patch constructed by dpkg-source.