a sponsoring DD (or DM)
can collaborate and publish using git.
-The sponsor must to be intending to use dgit for the upload.
+The sponsor must be intending to use dgit for the upload.
(If the sponsor does not use dgit,
it is not possible to properly publish
a sponsee's git branch.)
=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.
This disables a safety catch which would normally spot
situations where changes are accidentally lost.
When your sponsee is sending you source packages -
-perhaps multiple source pacakges with the same version number -
+perhaps multiple source packages with the same version number -
these safety catches are inevitably ineffective.
=head1 SEE ALSO