diff options
author | Sean Whitton <spwhitton@spwhitton.name> | 2016-10-30 18:15:35 -0700 |
---|---|---|
committer | Ian Jackson <ijackson@chiark.greenend.org.uk> | 2016-10-31 01:17:29 +0000 |
commit | a5871faec2c932db9255631dc094bc8f429b9f9a (patch) | |
tree | 3d1cf75dc33e6c2c14c1b366ada31c71287719b0 /dgit-sponsorship.7.pod | |
parent | 570229251d8c8c7fe65fe2117556d9b9e673306b (diff) |
dgit-sponsorship(7): Suggest supplying sample git-archive(1) cmds
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
Diffstat (limited to 'dgit-sponsorship.7.pod')
-rw-r--r-- | dgit-sponsorship.7.pod | 20 |
1 files changed, 16 insertions, 4 deletions
diff --git a/dgit-sponsorship.7.pod b/dgit-sponsorship.7.pod index 8feb0d1..ed37ff5 100644 --- a/dgit-sponsorship.7.pod +++ b/dgit-sponsorship.7.pod @@ -71,7 +71,10 @@ The git branch. =item * -Any .orig tarballs which will be needed. +Any .orig tarballs which will be needed, +or sample git-archive(1) +or gbp-buildpackage(1) +command(s) to generate them. =item * @@ -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) +or gbp-buildpackage(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. =over 4 @@ -138,7 +149,8 @@ or attach to the e-mail, if they are small. The sponsee should quote sha256sums of the .origs in their -handoff email. +handoff email, +unless they supplied commands to generate them. =back |