path: root/dgit-sponsorship.7.pod
diff options
authorSean Whitton <>2016-10-29 07:29:44 -0700
committerIan Jackson <>2016-10-30 17:14:31 +0000
commit5439ecadb25350a6a5a63097fcaeabaf656128e6 (patch)
tree0c4f3f798ec626e9e958765b6a345c8179bfa55d /dgit-sponsorship.7.pod
parent7b057ccd4fca9ada5be78a3a92513f7734d51aff (diff)
dgit-sponsorship(7): Demote to subsection
Signed-off-by: Sean Whitton <>
Diffstat (limited to 'dgit-sponsorship.7.pod')
1 files changed, 14 insertions, 4 deletions
diff --git a/dgit-sponsorship.7.pod b/dgit-sponsorship.7.pod
index 67d0647..3b8c3a8 100644
--- a/dgit-sponsorship.7.pod
+++ b/dgit-sponsorship.7.pod
@@ -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.
+=head2 git+origs based handoff
The elements of the handoff consists of:
@@ -92,7 +92,9 @@ 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.
@@ -108,7 +110,11 @@ Instead, the sponsee should include the
git commit id of their HEAD
in their handover email.
-=head2 orig tarballs
+=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.
@@ -134,7 +140,11 @@ if they are small.
The sponsee should quote sha256sums of the .origs in their
handoff email.
-=head2 quilt options
+=head3 quilt options
+=over 4
Some workflows involve git branches which are not natively