X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=dgit.git;a=blobdiff_plain;f=dgit-sponsorship.7.pod;h=3fc59d2f3ba5798a460ab6216f1cbe91465000fc;hp=8feb0d198657c53ece95685e80f8deef7beaeeaa;hb=68d88a087c25d9e1cee7106938ab4e9751cfa146;hpb=cd6e230475d630e1dc1e17e4142a27ad3eb3025d diff --git a/dgit-sponsorship.7.pod b/dgit-sponsorship.7.pod index 8feb0d19..3fc59d2f 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 @@ -233,7 +245,15 @@ or similar, to to the build, and then C to do the upload. -(If you switched to the quilt-cache dgit view, +(It is possible to upload from +the quilt-cache dgit view, +but this will cause the debian/1.2.3-1 tag to be +placed on this branch +rather than the sponsee's working branch. +Since this might be confusing, +it is a good idea to switch back to the sponsee's view, +after reviewing and before pushing. +If you do want to upload from the quilt-cache dgit view, B pass the --quilt or --gbp or --dpm option again.) If this was the first upload done with dgit,