Hi Andi, I've put a comment on LWN regarding mail topic and sent a comment linking to it on your blog (which apparently you did not accept, as it is still not visible there), but I didn't get any answer. Here is the story:
At the end of May I noticed that my semi-automatic git pulls fail on longterm/2.6.35.y. * linux-2.6.35.y 31f955d [longterm/2.6.35.y/master: ahead 106, behind 109] Release 2.6.35.13 remotes/longterm/2.6.35.y/master 4de01ac release-2.6.35.13 $ git log --oneline --cherry-pick --left-right linux-2.6.35.y...longterm/2.6.35.y/master >47764cf 2.6.35.13 longterm review >f60b63a Revert "tpm_tis: Use timeouts returned from TPM" >a374860 Revert "TPM: Long default timeout fix" >297a19b x86, microcode, AMD: Extend ucode size verification <012d9ae x86, microcode, AMD: Extend ucode size verification $ for B in linux-2.6.35.y longterm/2.6.35.y/master; do git log -1 --format=format:'%h %ai' $B; done 31f955d 2011-04-28 08:11:47 -0700 4de01ac 2011-04-28 08:21:24 -0700 $ git cat-file -p v2.6.35.13 object 31f955dba96c875076ced69e57071b79938f26d5 type commit tag v2.6.35.13 tagger Andi Kleen <[email protected]> Sun May 15 07:56:08 2011 -0700 Release 2.6.35.13 Correct tag this time. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEcBAABAgAGBQJNz+mWAAoJELKWlWCweoOzSP0H/Rh7wZ7rJQ4WcDWGrZ7aB5Vc v48Ovd1Hhfe7uDSg+r2jdwgxFu58mVyeFwkeGeH64FaOe+Xw9VBt7le6myReEkJz cwJU0UZu5H7PdyQGmIzzcDlWiYnGdsvHOZfGOzIpbDUFomsK+mSHfQ5IebRl0atX kDbPpTb7GGxOcS6hJ9mA5fMRFOYROjelqrqOYMvtCt96TcwxtoBeokZTuYqF9CRx q4ywKATQA7sk5rlAcB9tUrvsvJtdv3gp3c/ksZCylt83qvK1lKt9LyoFHLfMYZz7 c3Wr8XW6OsQ+z20DVwmnvj1vJ13aJocMy9nD6vDbHGBuiZPjsqZfYLNRXR5xpfY= =Wiuj -----END PGP SIGNATURE----- Something was broken there, because "fixed" tag was still pointing to the old release in my case. I know this repository is maybe not as important as mainline one, but why you haven't avoided destroying history that was already pushed? In case of mistake, 2.6.35.13 could be left as defunct and 2.6.35.14 would be the right one. To succeed you had to force push, so somehow I doubt it was a mistake, but independently of your motive you could at least notify somewhere about such re-release. Regards. -- Przemysław Pawełczyk _______________________________________________ stable mailing list [email protected] http://linux.kernel.org/mailman/listinfo/stable
