Clean-up of old SVN version tags

[Olly Betts]

James pointed out we had a lot of git branches with the naming pattern
svn/tags/* - these were created by git2svn from SVN tags, and most
are from tagging releases.  There's some use to having tags even for
ancient versions, but it'd be better to have them as git tags with
the standard naming scheme.

The short version is I've now created git tags for all the releases
which didn't have one, and removed these branches.  I also adjusted
the positions of some tags, so if you see removed/added/moved tags
for old releases, that's what's going on.

I haven't touched other SVN tags for now, but I plan to work through
those too, and likely also SVN branches and old git branches.

The details probably don't matter (this only affects tags for v1.1.5
and older which are long obsolete), but it seems good to record this
somewhere public in case this information is useful later.

A while ago (July 2024?) I went through and retrospectively created
missing version tags back to v0.7.0.  Today I went through and checked
if these were consistent with the SVN tags.  Generally they were with
some oddities, most of which I think are due to git2svn not always
accurately creating the history.  I've moved a few existing tags as a
result of this review - these were the retagging commands, which shows
old and new commit hashes:

$ git tag --force v0.9.7 96413bb8e3780debce3e64c961c56ca3bdb0fcc0
Updated tag 'v0.9.7' (was b061ad339c91)
$ git tag --force v0.9.10 a619e9ab13b7a60b7672eee4fc59d101cf49dcdf
Updated tag 'v0.9.10' (was 39ebe449a4a4)
$ git tag --force v1.0.10 63e8b370c60e1dc457cfe004a22f587aed68c451
Updated tag 'v1.0.10' (was e011207ddf0d)
$ git tag --force v1.0.12 9d544f494aa4b6434a4e7813150371a330d5ad72
Updated tag 'v1.0.12' (was e848bb556e26)
$ git tag --force v1.0.15 1887c3c817bdd4e942146e08fa0fee4dc5159597
Updated tag 'v1.0.15' (was 61263686c5b7)
$ git tag --force v1.0.17 58e47f3fea0b68a12c5e9093d17ae8895e94b439
Updated tag 'v1.0.17' (was 8993f436ce1c)
$ git tag --force v1.0.18 b6b4669c5fe40adb10fd70eb9f89e8b6c21af928
Updated tag 'v1.0.18' (was 78bc9c1b02b5)
$ git tag --force v1.0.19 081a172873f2d2d6310710418cd8f2f1a9cff0e7
Updated tag 'v1.0.19' (was 2fd37b508e8d)
$ git tag --force v1.1.4 173fa432181ff1dc8d5047366399c15de28361cb
Updated tag 'v1.1.4' (was b71767863d82)
$ git tag --force v1.1.5 a5bf02a4e87c65288d65300ff86b8c2067ffbb31
Updated tag 'v1.1.5' (was 45f05aa97ddc)

I have also created git tag v* to replace each branch svn/tags/*
which didn't already have a corresponding git tag.  In most cases the
tag points to the branch tip or its parent (svn2git created a dummy
commit for each tag, but sometimes this seems to remove or add a lot of
files and the parent commit looks a more sensible place to tag).

svn/tags/0.5.4 and 0.5.5 were in the wrong place (on commits in the
history of 0.5.3!) so I located appropriate commits to tag for these by
reviewing the short history of svn/branch-0.5.

Cheers,
    Olly
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.xapian.org/pipermail/xapian-discuss/attachments/20260401/950713d4/attachment.sig>