summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSean Whitton <spwhitton@spwhitton.name>2016-10-29 07:29:08 -0700
committerIan Jackson <ijackson@chiark.greenend.org.uk>2016-10-30 17:14:31 +0000
commitc316aea690adbd7c1701043b7addac4a8adbf36d (patch)
treee6433145e6e86541d47f9f91a0d236efc88d32ec
parent1e4e44e19d1e2b24c1d7b4cbb0057662ee8434ee (diff)
dgit-sponsorship(7): Mention RFS procedure
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
-rw-r--r--dgit-sponsorship.7.pod6
1 files changed, 4 insertions, 2 deletions
diff --git a/dgit-sponsorship.7.pod b/dgit-sponsorship.7.pod
index 40410e1..45889fc 100644
--- 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
-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.
@@ -89,6 +89,8 @@ constraints about upload timing, etc.
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
@@ -162,7 +164,7 @@ This part is addressed to the sponsor:
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,