summaryrefslogtreecommitdiff
path: root/dgit-sponsorship.7.pod
diff options
context:
space:
mode:
authorSean Whitton <spwhitton@spwhitton.name>2023-10-16 11:26:14 +0100
committerSean Whitton <spwhitton@spwhitton.name>2023-10-16 11:26:48 +0100
commit20d37e75b10c49a5c633a0c9e24371e35e1d0932 (patch)
tree7dc532fd542d9aed35ef4aeb1b64811b06b06e27 /dgit-sponsorship.7.pod
parent56ffa6a7de9cc41a72a309ea8c7308a41e61fc04 (diff)
dgit-sponsorship(7): Mention git-deborig(1) alongside git-archive(1)
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
Diffstat (limited to 'dgit-sponsorship.7.pod')
-rw-r--r--dgit-sponsorship.7.pod9
1 files changed, 6 insertions, 3 deletions
diff --git a/dgit-sponsorship.7.pod b/dgit-sponsorship.7.pod
index 91e70c7..7949279 100644
--- a/dgit-sponsorship.7.pod
+++ b/dgit-sponsorship.7.pod
@@ -72,7 +72,8 @@ The git branch.
=item *
Any .orig tarballs which will be needed,
-or sample git-archive(1)
+or sample git-deborig(1),
+git-archive(1)
or gbp-buildpackage(1)
command(s) to generate them.
@@ -120,9 +121,11 @@ 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.
-If the sponsee generated these tarballs with git-archive(1)
+If the sponsee generated these tarballs with
+git-deborig(1), git-archive(1)
or gbp-buildpackage(1),
-they can simply include a sample invocation of git-archive(1)
+they can simply include a sample invocation of
+git-deborig(1) or git-archive(1)
or ensure that a suitable gbp.conf is present
in the source package
to generate the tarball.