diff options
| author | Ian Jackson <ijackson@chiark.greenend.org.uk> | 2022-09-04 11:27:06 +0100 |
|---|---|---|
| committer | Ian Jackson <ijackson@chiark.greenend.org.uk> | 2022-09-04 12:36:11 +0100 |
| commit | d6ce5696754c895926e122ed9b4690703dcdb78a (patch) | |
| tree | f5d491efbfdca4bfe1d2aac3ebdd60cd3d8da375 /dgit-sponsorship.7.pod | |
| parent | 2df2d6795e7ef7f34fb9a52236ecc9e8d40145fa (diff) | |
docs: Update for changes to dgit push-*, and recommend push-source
In command line runes and examples, generally change to
"dgit push-source".
In running text whwere we talk about "push or push-source", change to
"push-built or push-source".
In running text where we talk loosely about "push", leave it that way.
Closes: #992606
Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
Diffstat (limited to 'dgit-sponsorship.7.pod')
| -rw-r--r-- | dgit-sponsorship.7.pod | 15 |
1 files changed, 8 insertions, 7 deletions
diff --git a/dgit-sponsorship.7.pod b/dgit-sponsorship.7.pod index 2e6f82d..91e70c7 100644 --- a/dgit-sponsorship.7.pod +++ b/dgit-sponsorship.7.pod @@ -30,7 +30,7 @@ This section is addressed to the sponsee: =head2 General You should prepare the package as if you were going -to upload it with C<dgit push-source> or C<dgit push> yourself. +to upload it with C<dgit push-source> or C<dgit push-built> yourself. For a straightforward NMU, consult L<dgit-nmu-simple(7)>. @@ -78,7 +78,7 @@ command(s) to generate them. =item * -A sample dgit push command, containing +A sample dgit push-source command, containing any dgit --quilt=, --gbp or --dpm option needed =item * @@ -160,7 +160,7 @@ Some workflows involve git branches which are not natively dgit-compatible. Normally dgit will convert them as needed, during push. -Supply a sample "dgit push" command +Supply a sample "dgit push-source" command including any C<--gbp> (aka C<--quilt=gbp>), C<--dpm> (aka C<--quilt=dpm>), @@ -170,7 +170,7 @@ e.g. =over 4 - % dgit --gbp push + % dgit --gbp push-source =back @@ -236,7 +236,7 @@ C<dgit -wgf [--quilt=...] sbuild -A -C> or similar, to to the build, and then C<dgit -wgf [--quilt=...] push-source> or -C<dgit -wgf [--quilt=...] push> +C<dgit -wgf [--quilt=...] push-built> to do the upload. Check whether the sponsee made a debian/I<version> tag. @@ -306,8 +306,9 @@ formatted as a dgit branch. When you have finished your review and your tests, you can do the -dgit sbuild and -dgit push directly from the "sponsee" branch. +dgit push-source +(or dgit sbuild and dgit push-built) +directly from the "sponsee" branch. You will need to pass C<--overwrite> |