=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)>.
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.
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.
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.
C<--overwrite>
to dgit.
+Alternatively,
+if this was the first ever dgit push of the package,
+you can pass C<--deliberately-not-fast-forward>
+instead of C<--overwrite>.
+This avoids introducing a new origin commit
+into the dgit view of
+the sponsee's git history
+which is unnecessary and could be confusing.
=head1 SPONSORING A NON-GIT-USING SPONSEE