path: root/dgit.1
diff options
authorIan Jackson <>2015-06-30 21:10:30 +0100
committerIan Jackson <>2015-06-30 21:10:30 +0100
commite32ec25d687126038f441f4ffa11bc699de847dc (patch)
treed5013c3882da39a76d61aa0e5655cf53827fa302 /dgit.1
parent02664d80306d561e03cde2108a6dc5ee7626d6a3 (diff)
Document that dgit repos are cloneable with git, in dgit(1) section MODEL. [Andreas Barth.] Closes:#768470.
Diffstat (limited to 'dgit.1')
1 files changed, 4 insertions, 0 deletions
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.