Document that dgit repos are cloneable with git, in dgit(1) section MODEL. [Andreas...

[dgit.git] / dgit.1

diff --git a/dgit.1 b/dgit.1
index a33dcb7ef6ba0740e6ad7d3d24ddabf2765a27f5..9705f0af2403abc84d2a07f07410dd6fb80125b0 100644 (file)
--- 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.