summaryrefslogtreecommitdiff
path: root/dgit-sponsorship.7.pod
diff options
context:
space:
mode:
Diffstat (limited to 'dgit-sponsorship.7.pod')
-rw-r--r--dgit-sponsorship.7.pod8
1 files changed, 5 insertions, 3 deletions
diff --git a/dgit-sponsorship.7.pod b/dgit-sponsorship.7.pod
index 0808329..3fbdac8 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> yourself.
+to upload it with C<dgit push-source> or C<dgit push> yourself.
For a straightforward NMU, consult L<dgit-nmu-simple(7)>.
@@ -102,7 +102,7 @@ against the sponsorship-requests pseudo-package.
The sponsee should push their HEAD as a git branch
to any suitable git server.
They can use their own git server;
-alioth is another possibility.
+salsa is another possibility.
The branch names used by the sponsee on their local machine,
and on the server, do not matter.
@@ -220,7 +220,7 @@ C<dgit fetch sid> will get you an up-to-date
C<refs/remotes/dgit/dgit/sid>
showing what's in the archive already.
-C<dgit -wgf --damp-run push>
+C<dgit -wgf --damp-run push-source>
will check that dgit can build an appropriate source package.
There is no need to run debdiff.
@@ -234,6 +234,8 @@ When you have completed your source review,
and use
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>
to do the upload.