-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Gary V. Vaughan on 4/16/2008 7:31 PM: | Ah, the link that was giving me a 403 was picking up a spurious trailing | paren. So now I see two near identical pages: | | http://git.sv.gnu.org/gitweb/?p=libtool.git;a=commit;h=2bbe5d | http://git.sv.gnu.org/gitweb/?p=libtool.git;a=commit;h=724f291 | | The difference being that one of them, as Eric correctly noted, leads to | another page without the release-2-2-2 tag.
More importantly, the one with the release-2-2-2 tag has the wrong history. | | So my question is how did you find the stale tags? I was browsing gitweb, and noticed that the shortlog for release-2-2-2 has a yellow box showing the existing tag, but the shortlog for master does not: http://git.sv.gnu.org/gitweb/?p=libtool.git;a=shortlog;h=refs/tags/release-2-2-2 Closer investigation shows that the two commits, although they have identical summaries, have different SHA1 and thus different histories. To confirm it, you can do: $ git log 2bbe5d..724f291 --pretty=oneline |wc ~ 3018 66346 611845 Wow - they differ by more than 3000 commits (likely, they share a common ancestor over 1500 commits ago). - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkgGr4UACgkQ84KuGfSFAYA5UgCgxSgCMJwZjEPOqkAfdVsOfSfQ ccYAoMvoh/gylhqGvk6W4J14clWW3ol6 =eNhv -----END PGP SIGNATURE----- _______________________________________________ http://lists.gnu.org/mailman/listinfo/libtool
