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 35a09223fdeff8d7a025b15336c64c4f814ef256..9705f0af2403abc84d2a07f07410dd6fb80125b0 100644 (file)
--- a/dgit.1
+++ b/dgit.1
@@ -167,7 +167,17 @@ Pushes the contents of the specified directory on a remote machine.
 This is like running dgit push on build-host with build-dir as the
 current directory; however, signing operations are done on the
 invoking host.  This allows you to do a push when the system which has
 This is like running dgit push on build-host with build-dir as the
 current directory; however, signing operations are done on the
 invoking host.  This allows you to do a push when the system which has

-the source code and the build outputs has no access to the key.
+the source code and the build outputs has no access to the key:
+
+1.     Clone on build host (dgit clone)
+.br
+2.     Edit code on build host (edit, git commit)
+.br
+3.     Build package on build host (dgit build)
+.br
+4.     Test package on build host or elsewhere (dpkg -i, test)
+.br
+5.     Upload by invoking dgit rpush on host with your GPG key.

 
 However, the build-host must be able to ssh to the dgit repos.  If
 this is not already the case, you must organise it separately, for
 
 However, the build-host must be able to ssh to the dgit repos.  If
 this is not already the case, you must organise it separately, for


@@ -202,6 +212,10 @@ ask it to generate a single squashed patch instead.
 .TP
 .B dgit version
 Prints version information and exits.
 .TP
 .B dgit version
 Prints version information and exits.

+.TP
+.BI "dgit clone-dgit-repos-server" " destdir"
+Tries to fetch a copy of the source code for the dgit-repos-server,
+as actually being used on the dgit git server, as a git tree.

 .SH OPTIONS
 .TP
 .BR --dry-run | -n
 .SH OPTIONS
 .TP
 .BR --dry-run | -n


@@ -278,6 +292,11 @@ option after verifying that: none of the rejected-from-NEW (or
 never-accepted) versions in the git history of your current push, were
 rejected by ftpmaster for copyright or redistributability reasons.
 .TP
 never-accepted) versions in the git history of your current push, were
 rejected by ftpmaster for copyright or redistributability reasons.
 .TP

+.BR --deliberately-fresh-repo
+Declare that you are deliberately rewinding history and want to
+throw away the existing repo.  Not relevant when pushing to Debian,
+as the Debian server will do this automatically when necessary.
+.TP

 .BR --quilt=linear
 When fixing up source format `3.0 (quilt)' metadata, insist on
 generating a linear patch stack.  If such a stack cannot be generated,
 .BR --quilt=linear
 When fixing up source format `3.0 (quilt)' metadata, insist on
 generating a linear patch stack.  If such a stack cannot be generated,


@@ -577,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.
 
 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.
 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.