From 5439ecadb25350a6a5a63097fcaeabaf656128e6 Mon Sep 17 00:00:00 2001 From: Sean Whitton Date: Sat, 29 Oct 2016 07:29:44 -0700 Subject: dgit-sponsorship(7): Demote to subsection Signed-off-by: Sean Whitton --- dgit-sponsorship.7.pod | 18 ++++++++++++++---- 1 file 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 or C, 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: @@ -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 +=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. @@ -134,7 +140,11 @@ if they are small. 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. -- cgit v1.2.3