|author||Sean Whitton <firstname.lastname@example.org>||2016-10-30 18:15:35 -0700|
|committer||Ian Jackson <email@example.com>||2016-10-31 01:17:29 +0000|
dgit-sponsorship(7): Suggest supplying sample git-archive(1) cmds
Signed-off-by: Sean Whitton <firstname.lastname@example.org>
Diffstat (limited to 'dgit-sponsorship.7.pod')
1 files changed, 16 insertions, 4 deletions
diff --git a/dgit-sponsorship.7.pod b/dgit-sponsorship.7.pod
index 8feb0d1..ed37ff5 100644
@@ -71,7 +71,10 @@ The git branch.
-Any .orig tarballs which will be needed.
+Any .orig tarballs which will be needed,
+or sample git-archive(1)
+command(s) to generate them.
@@ -119,8 +122,16 @@ in their handover email.
If there are any .origs that are not in the archive already,
the sponsor will need them as part of the upload.
-The simplest approach is to
-commit them with pristine-tar(1), e.g.
+If the sponsee generated these tarballs with git-archive(1)
+they can simply include a sample invocation of git-archive(1)
+or ensure that a suitable gbp.conf is present
+in the source package
+to generate the tarball.
+Otherwise, the simplest approach is to
+commit the orig tarballs
+with pristine-tar(1), e.g.
@@ -138,7 +149,8 @@ or attach to the e-mail,
if they are small.
The sponsee should quote sha256sums of the .origs in their
+unless they supplied commands to generate them.