Hi Ludo, On Fri, 02 Sep 2022 at 15:17, Ludovic Courtès <l...@gnu.org> wrote:
> Here you would need ‘--allow-downgrades’. Maybe time-machine could advertise of this option? Well aside, it can be indeed confusing that the version-1.x branch does not match the tag v1.x; I understand why. --8<---------------cut here---------------start------------->8--- $ git log --graph --format="%h %s %d" v1.0.0^..origin/version-1.0.0 * 48aa30ce73 build: Add 'doc/build.scm' to build on-line copies of the manual. (origin/version-1.0.0) * adf577dcc4 doc: Update htmlxref.cnf. * 1a9fc8e228 doc: Warn about missing entries in htmlxref.cnf. * 2921b6a611 doc: Adjust cross-references for GNU triplets. * 3aa11dfbed doc: Provide the actual URL to the VM image. * 542e7fb57f doc: Add note about <https://bugs.gnu.org/35541>. * 3a3e9f2bb5 guix-install.sh: Update URL. * 9c941364bf vm: Build ISOs and VM images in a UTF-8 environment. * 17acc215bf gnu: guix: Update to 326dcbf. * 326dcbf1b3 gnu: guix: Update to 1.0.0. * 6298c3ffd9 Update NEWS. (tag: v1.0.0) --8<---------------cut here---------------end--------------->8--- Does it make sense to document it? And does it make sense to merge to master right after 326dcbf1b3? And not after some commits: --8<---------------cut here---------------start------------->8--- $ for i in $(seq 0 3); do \ git log --graph --format="%h %s %d" v1.$i.0^..origin/version-1.$i.0 \ | wc -l ;done 11 6 warning: refname 'v1.2.0' is ambiguous. 10 7 --8<---------------cut here---------------end--------------->8--- Cheers, simon