Re: Have git SHA1 ID's changed in the last 5 years?

[David Kastrup]

Mark Polesky <address@hidden> writes:

> Ha!  My old repo stops a day before that change.  No wonder I abandoned
> it...  Okay, when I have some time I'll start updating the small handful of
> mislabeled committishes.  It's not that many.

Here are the tags that apparently have a history ending in the fred
starting commit, keeping it alive in our repository.

git tag --contains 0ff96d5d41379dbb968507fd848642da518dc50b
release/1.5.59
release/1.5.60
release/1.5.71
release/1.7.25
release/1.7.28
release/1.7.29
release/1.9.5
release/2.1.10
release/2.1.11
release/2.1.12
release/2.1.13
release/2.1.14
release/2.1.15
release/2.1.16
release/2.1.17
release/2.1.18
release/2.1.19
release/2.1.20
release/2.1.21
release/2.1.22
release/2.1.27
release/2.1.3
release/2.1.36
release/2.1.4
release/2.1.5
release/2.1.6
release/2.1.7
release/2.1.8
release/2.1.9
release/2.3.12
release/2.3.24
release/2.3.9
release/2.5.23
release/2.5.32
release/2.6.4
release/2.7.16
release/2.7.2
release/2.7.20
release/2.7.38
release/2.8.2
start


So what's up with them?

Jan, any idea?  Apparently you did the conversion.

If I use
git tag -l --contains 0ff96d5d41379dbb968507fd848642da518dc50b -n

I get
release/1.5.59  This commit was manufactured by cvs2svn to create tag 
'lilypond_1_5_59'.
release/1.5.60  This commit was manufactured by cvs2svn to create tag 
'lilypond_1_5_60'.
release/1.5.71  This commit was manufactured by cvs2svn to create tag 
'lilypond_1_5_71'.
release/1.7.25  This commit was manufactured by cvs2svn to create tag 
'lilypond_1_7_25'.
release/1.7.28  This commit was manufactured by cvs2svn to create tag 
'lilypond_1_7_28'.
release/1.7.29  This commit was manufactured by cvs2svn to create tag 
'lilypond_1_7_29'.
release/1.9.5   This commit was manufactured by cvs2svn to create tag 
'lilypond_1_9_5'.
release/2.1.10  This commit was manufactured by cvs2svn to create tag 
'lilypond_2_1_10'.
release/2.1.11  This commit was manufactured by cvs2svn to create tag 
'lilypond_2_1_11'.
release/2.1.12  This commit was manufactured by cvs2svn to create tag 
'lilypond_2_1_12'.
release/2.1.13  This commit was manufactured by cvs2svn to create tag 
'lilypond_2_1_13'.
release/2.1.14  This commit was manufactured by cvs2svn to create tag 
'lilypond_2_1_14'.
release/2.1.15  This commit was manufactured by cvs2svn to create tag 
'lilypond_2_1_15'.
release/2.1.16  This commit was manufactured by cvs2svn to create tag 
'lilypond_2_1_16'.
release/2.1.17  This commit was manufactured by cvs2svn to create tag 
'lilypond_2_1_17'.
release/2.1.18  This commit was manufactured by cvs2svn to create tag 
'lilypond_2_1_18'.
release/2.1.19  This commit was manufactured by cvs2svn to create tag 
'lilypond_2_1_19'.
release/2.1.20  This commit was manufactured by cvs2svn to create tag 
'lilypond_2_1_20'.
release/2.1.21  This commit was manufactured by cvs2svn to create tag 
'lilypond_2_1_21'.
release/2.1.22  This commit was manufactured by cvs2svn to create tag 
'lilypond_2_1_22'.
release/2.1.27  This commit was manufactured by cvs2svn to create tag 
'lilypond_2_1_27'.
release/2.1.3   This commit was manufactured by cvs2svn to create tag 
'lilypond_2_1_3'.
release/2.1.36  This commit was manufactured by cvs2svn to create tag 
'lilypond_2_1_36'.
release/2.1.4   This commit was manufactured by cvs2svn to create tag 
'lilypond_2_1_4'.
release/2.1.5   This commit was manufactured by cvs2svn to create tag 
'lilypond_2_1_5'.
release/2.1.6   This commit was manufactured by cvs2svn to create tag 
'lilypond_2_1_6'.
release/2.1.7   This commit was manufactured by cvs2svn to create tag 
'lilypond_2_1_7'.
release/2.1.8   This commit was manufactured by cvs2svn to create tag 
'lilypond_2_1_8'.
release/2.1.9   This commit was manufactured by cvs2svn to create tag 
'lilypond_2_1_9'.
release/2.3.12  This commit was manufactured by cvs2svn to create tag 
'lilypond_2_3_12'.
release/2.3.24  This commit was manufactured by cvs2svn to create tag 
'lilypond_2_3_24'.
release/2.3.9   This commit was manufactured by cvs2svn to create tag 
'lilypond_2_3_9'.
release/2.5.23  This commit was manufactured by cvs2svn to create tag 
'lilypond_2_5_23'.
release/2.5.32  This commit was manufactured by cvs2svn to create tag 
'lilypond_2_5_32'.
release/2.6.4   This commit was manufactured by cvs2svn to create tag 
'lilypond_2_6_4'.
release/2.7.16  This commit was manufactured by cvs2svn to create tag 
'lilypond_2_7_16'.
release/2.7.2   This commit was manufactured by cvs2svn to create tag 
'lilypond_2_7_2'.
release/2.7.20  This commit was manufactured by cvs2svn to create tag 
'lilypond_2_7_20'.
release/2.7.38  This commit was manufactured by cvs2svn to create tag 
'lilypond_2_7_38'.
release/2.8.2   This commit was manufactured by cvs2svn to create tag 
'lilypond_2_8_2'.
start           This commit was manufactured by cvs2svn to create tag 'start'.

So it seems likely that those are left from some earlier conversion.  If
I read "man git-tag" below "DISCUSSION", it would seem like retagging is
an ugly thing once tags have been published with different content.

-- 
David Kastrup