X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=dgit.git;a=blobdiff_plain;f=dgit-maint-merge.7.pod;h=71f701e196a2196db084db9c106587b269a424a3;hp=6d0db9919c356c56756094d91dc24b1c0c091ece;hb=e31362aa5853ada39b14be5bbdc46cbda58e20a6;hpb=1cc88d94aef2a09baa3f0cbeb1a1c652f639523b diff --git a/dgit-maint-merge.7.pod b/dgit-maint-merge.7.pod index 6d0db991..71f701e1 100644 --- a/dgit-maint-merge.7.pod +++ b/dgit-maint-merge.7.pod @@ -52,6 +52,16 @@ compress orig tarballs: =head1 INITIAL DEBIANISATION +=head2 When upstream tags releases in git and releases identical tarballs + +Ideally upstream would make git tags, and tarball releases, which are +completely identical to each other. If this is the case then you can +use the upstream tarballs directly. + +If you're not sure, use the procedure below under "When upstream +releases only tarballs" only with a different upstream tag name. Then +use git diff to check that there are no differences. + =head2 When upstream tags releases in git Suppose that the latest stable upstream release is 1.2.2, and this has @@ -124,7 +134,7 @@ Now create I: =over 4 [DEFAULT] - upstream-branch = upsteram + upstream-branch = upstream debian-branch = master upstream-tag = %(version)s @@ -296,7 +306,11 @@ We create a DFSG-clean tag to merge to master: Before merging the new 1.2.3+dfsg tag to master, you should first determine whether it would be legally dangerous for the non-free material to be publicly accessible in the git history on -B. If it would be, pass B<--squash> to git-merge(1). +B. +If it would be dangerous, there is a big problem; +in this case please consult your archive administrators +(for Debian this is the dgit administrator dgit-owner@debian.org +and the ftpmasters ftpmaster@ftp-master.debian.org). =head2 When upstream releases only tarballs