summary |
shortlog |
log |
commit | commitdiff |
tree
raw |
patch |
inline | side by side (from parent 1:
5702292)
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
-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.
If there are any .origs that are not in the archive already,
the sponsor will need them as part of the upload.
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.
if they are small.
The sponsee should quote sha256sums of the .origs in their
if they are small.
The sponsee should quote sha256sums of the .origs in their
+handoff email,
+unless they supplied commands to generate them.