X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=dgit.git;a=blobdiff_plain;f=dgit.1;h=1460938a4e5f329be38385b287b9683b01f12671;hp=d5ef9303923240dbc745e0f2fad5cf06b081281d;hb=177768519130da7d21705598f2b5d961cf408a4b;hpb=441a1663d98b29d735e2d9392a5cfc84d7cf00f0 diff --git a/dgit.1 b/dgit.1 index d5ef9303..1460938a 100644 --- a/dgit.1 +++ b/dgit.1 @@ -46,6 +46,7 @@ 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 +dgit-downstream-dsc(7) setting up dgit push for a new distro .TE .LP See \fBdgit(7)\fP for detailed information about the data @@ -124,6 +125,11 @@ NB: dgit checkout will only do a fetch if it has to. If you already have the suite branch, and want to merge your branch with updates from the archive, use dgit pull. + +dgit checkout will normally need to aceess the archive server, +to canonicalise the provided suite name. +The exception is if you specify the canonical name, +and the branch (or tracking branch) already exists. .TP \fBdgit build\fR ... Runs @@ -222,9 +228,6 @@ 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 @@ -234,6 +237,9 @@ for source package upload and push. 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. @@ -1045,6 +1051,17 @@ The result is a fresh import, discarding the git history that the person who pushed that .dsc was working with. .TP +.B --force-uploading-binaries +Carry on and +upload binaries +even though dgit thinks your distro does not permit that. +.TP +.B --force-uploading-source-only +Carry on and do a source-only upload, +without any binaries, +even though dgit thinks your distro does not permit that, +or does not permit that in this situation. +.TP .B --force-unrepresentable Carry on even if dgit thinks that your git tree contains changes @@ -1221,6 +1238,8 @@ or when pushing and .TP .BI dgit-distro. distro .rewrite-map-enable .TP +.BR dgit-distro. \fIdistro\fR .source-only-uploads " " ok | always | never | not-wholly-new +.TP .BI dgit.default.old-dsc-distro .TP .BI dgit.dsc-url-proto-ok. protocol