dgit-maint-gbp(7): Mention --overwrite

[dgit.git] / dgit-sponsorship.7.pod

diff --git a/dgit-sponsorship.7.pod b/dgit-sponsorship.7.pod
index 40410e143cbed193ebc0edb8041a6393e5220a0d..9fe8abc7809e37efa90f56b568f45211d4e5b05a 100644 (file)
--- a/dgit-sponsorship.7.pod
+++ b/dgit-sponsorship.7.pod
@@ -6,7 +6,7 @@ dgit-sponsorship - tutorial for Debian upload sponsorship, using git
 
 This tutorial describes how a Debian sponsored contributor
 and
 
 This tutorial describes how a Debian sponsored contributor
 and

-their sponsoring DD (or DM)
+a sponsoring DD (or DM)

 can collaborate and publish using git.
 
 The sponsor must to be intending to use dgit for the upload.
 can collaborate and publish using git.
 
 The sponsor must to be intending to use dgit for the upload.


@@ -59,7 +59,7 @@ options to dgit, or
 C<dgit --gbp> or C<dgit --dpm>,
 you must specify that in your handoff email - see below.
 
 C<dgit --gbp> or C<dgit --dpm>,
 you must specify that in your handoff email - see below.
 

-=head1 GIT+ORIGS BASED HANDOFF
+=head2 git+origs based handoff

 
 The elements of the handoff consists of:
 
 
 The elements of the handoff consists of:
 


@@ -89,8 +89,12 @@ constraints about upload timing, etc.
 
 If the handoff is done by email,
 the elements above should be a in a single, signed, message.
 
 If the handoff is done by email,
 the elements above should be a in a single, signed, message.

+This could be an RFS submission
+against the sponsorship-requests pseudo-package.

 
 

-=head2 git branch
+=head3 git branch
+
+=over 4

 
 The sponsee should push their HEAD as a git branch
 to any suitable git server.
 
 The sponsee should push their HEAD as a git branch
 to any suitable git server.


@@ -102,11 +106,15 @@ and on the server, do not matter.
 
 The sponsee should not make a C<debian/>I<version> tag.
 
 
 The sponsee should not make a C<debian/>I<version> tag.
 

-Instead, the sponsor should include the
+Instead, the sponsee should include the

 git commit id of their HEAD
 in their handover email.
 
 git commit id of their HEAD
 in their handover email.
 

-=head2 orig tarballs
+=back
+
+=head3 orig tarballs
+
+=over 4

 
 If there are any .origs that are not in the archive already,
 the sponsor will need them as part of the upload.
 
 If there are any .origs that are not in the archive already,
 the sponsor will need them as part of the upload.


@@ -132,7 +140,11 @@ if they are small.
 The sponsee should quote sha256sums of the .origs in their
 handoff email.
 
 The sponsee should quote sha256sums of the .origs in their
 handoff email.
 

-=head2 quilt options
+=back
+
+=head3 quilt options
+
+=over 4

 
 Some workflows involve git branches which are not natively
 dgit-compatible.
 
 Some workflows involve git branches which are not natively
 dgit-compatible.


@@ -162,11 +174,12 @@ This part is addressed to the sponsor:
 
 You should check the signature on the email.
 
 
 You should check the signature on the email.
 

-Use C<git fetch> to fetch the git branch
+Use C<git fetch> or C<git clone> to obtain the git branch

 prepared by your sponsee,
 and obtain any .origs mentioned by the sponsee
 (to extract .origs committed with pristine-tar,
 prepared by your sponsee,
 and obtain any .origs mentioned by the sponsee
 (to extract .origs committed with pristine-tar,

-you can use origtargz(1).)
+you can use origtargz(1),
+or use "gbp clone --pristine-tar".)

 
 Check the git commit ID of the sponsee's branch tip,
 and the sha256sums of the .origs,
 
 Check the git commit ID of the sponsee's branch tip,
 and the sha256sums of the .origs,