X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=dgit.git;a=blobdiff_plain;f=dgit.1;h=c5d76884871315a815cfa6f2dd6fbd24de8d8726;hp=4f1479884d1d73b57019ad50d75917185a531496;hb=5099a42730ecb2a33152826a623d545f60fea77e;hpb=b5bcafcd708628c57619139032c093ccf3694597 diff --git a/dgit.1 b/dgit.1 index 4f147988..c5d76884 100644 --- a/dgit.1 +++ b/dgit.1 @@ -39,10 +39,11 @@ This is the command line reference. Please read the tutorial(s): .TS lb l. -dgit-user(7) for users: editing, building and sharing packages -dgit-nmu-simple(7) for DDs: doing a straightforward NMU +dgit-user(7) for users: edit, build and share packages +dgit-nmu-simple(7) for DDs: do a straightforward NMU dgit-maint-native(7) for maintainers of Debian-native packages -dgit-maint-merge(7) for maintainers who want a pure git workflow +dgit-maint-debrebase(7) for maintainers: a pure-git rebasish workflow +dgit-maint-merge(7) for maintainers: a pure-git merging workflow dgit-maint-gbp(7) for maintainers already using git-buildpackage dgit-sponsorship(7) for sponsors and sponsored contributors .TE @@ -127,7 +128,8 @@ The output is left in and .IR package \fB_\fR version \fB_source.changes\fR. -Tagging, signing and actually uploading should be left to dgit push. +Tagging, signing and actually uploading should be left to dgit +push-source, or dgit push. .TP .B dgit clean Cleans the current working tree (according to the --clean= option in @@ -184,14 +186,19 @@ archive. dgit push always uses the package, suite and version specified in the debian/changelog and the .dsc, which must agree. If the command line specifies a suite then that must match too. + +With \fB-C\fR, performs a dgit push, additionally ensuring that no +binary packages are uploaded. + +When used on a git-debrebase branch, +dgit calls git-debrebase +to prepare the branch +for source package upload and push. .TP \fBdgit push-source\fR [\fIsuite\fP] Without \fB-C\fR, builds a source package and dgit pushes it. Saying \fBdgit push-source\fR is like saying "update the source code in the archive to match my git HEAD, and let the autobuilders do the rest." - -With \fB-C\fR, performs a dgit push, additionally ensuring that no -binary packages are uploaded. .TP \fBdgit rpush\fR \fIbuild-host\fR\fB:\fR\fIbuild-dir\fR [\fIpush args...\fR] Pushes the contents of the specified directory on a remote machine. @@ -261,10 +268,19 @@ For why, see in .BR dgit(7) . +If there is an existing macro attribute line +.B [attr]dgit-defuse-attrs +in .git/info/attributes, +but it is insufficient, +because it was made by an earlier version of dgit +and git has since introduced new transforming attributes, +modifies the macro to disable the newer transformations. + (If there is already a macro attribute line .B [attr]dgit-defuse-attrs in .git/info/attributes -(whatever its effects), +which does what dgit requires +(whatever files it effects), this operation does nothing further. This fact can be used to defeat or partially defeat dgit setup-gitattributes @@ -285,6 +301,15 @@ new quilt patch. dgit cannot convert nontrivial merges, or certain other kinds of more exotic history. If dgit can't find a suitable linearisation of your history, by default it will fail, but you can ask it to generate a single squashed patch instead. + +When used with a git-debrebase branch, +dgit will ask git-debrebase to prepare patches. +However, +dgit can make patches in some situations where git-debrebase fails, +so dgit quilt-fixup can be useful in its own right. +To always use dgit's own patch generator +instead of git-debrebase make-patches, +pass --git-debrebase=true to dgit. .TP \fBdgit import-dsc\fR [\fIsub-options\fR] \fI../path/to/.dsc\fR [\fB+\fR|\fB..\fR]branch Import a Debian-format source package, @@ -824,6 +849,7 @@ Specifies a single additional option to pass to .BR sbuild , .BR ssh , .BR dgit , +.BR git-debrebase , .BR apt-get , .BR apt-cache , .BR gbp-pq , @@ -871,6 +897,7 @@ Specifies alternative programs to use instead of .BR gpg , .BR ssh , .BR dgit , +.BR git-debrebase , .BR apt-get , .BR apt-cache , .BR git ,