X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=dgit-sponsorship.7.pod;h=8d5b72daa2de1e42b11820c132cda72c260d3ce9;hb=4f89b4d20f0663710396f37b3b53fd32cc71b090;hp=ed37ff5f1107956f49536a93850d52778ea28b81;hpb=a5871faec2c932db9255631dc094bc8f429b9f9a;p=dgit.git
diff --git a/dgit-sponsorship.7.pod b/dgit-sponsorship.7.pod
index ed37ff5f..8d5b72da 100644
--- a/dgit-sponsorship.7.pod
+++ b/dgit-sponsorship.7.pod
@@ -107,8 +107,6 @@ alioth is another possibility.
The branch names used by the sponsee on their local machine,
and on the server, do not matter.
-The sponsee should not make a CI tag.
-
Instead, the sponsee should include the
git commit id of their HEAD
in their handover email.
@@ -197,12 +195,6 @@ Check the git commit ID of the sponsee's branch tip,
and the sha256sums of the .origs,
against the handoff email.
-Confirm that the sponsee has not made
-a debian/1.2.3-1 tag.
-If they have,
-it is best to ask them to delete it now,
-as it can cause confusion later when dgit push produces its own tag.
-
Now you can check out the branch tip,
and do your substantive review.
@@ -245,8 +237,20 @@ or similar, to to the build, and then
C
to do the upload.
-(If you switched to the quilt-cache dgit view,
-B pass the --quilt or --gbp or --dpm option again.)
+Check whether the sponsee made a debian/I tag.
+If they did,
+ensure you have their tag in the repository you are pushing from,
+or pass C<--no-dep14tag>.
+This avoids identically named, non-identical tags,
+which can be confusing.
+
+(It is possible to upload from
+the quilt-cache dgit view.
+If you want to do this,
+B pass the C<--quilt> or C<--gbp> or C<--dpm> options again,
+and B pass C<--no-dep14tag>,
+since the debian/I tag
+should go on the sponsee's branch.)
If this was the first upload done with dgit,
you may need to pass