<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Git history is broken; prevents github upload" href="https://bugs.freedesktop.org/show_bug.cgi?id=94737#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Git history is broken; prevents github upload" href="https://bugs.freedesktop.org/show_bug.cgi?id=94737">bug 94737</a> from <a class="email" href="mailto:daniel@fooishbar.org" title="Daniel Stone <daniel@fooishbar.org>"> Daniel Stone</a> <pre>(In reply to Emil Velikov from <a href="show_bug.cgi?id=94737#c4">comment #4</a>) > There is a bit more info (including a link to possible git fix) [1]. Fwiw > I'm all for creating a mirror of mesa, libdrm and/or others on github, > although the tags will need to be manually resolved. Indeed. > Afaics most/all of them are signed, thus removing them from fd.o will be > impossible without rewriting git history ? Not that I'm aware of ... ? Tags are individual standalone Git objects, with no references to them other than requesting the list of tags from the server, so removing these objects has no effect on any other objects (the usual sense of rewriting history). It's true that the ones to be preserved would need to be recreated; from what I understand, this would require a manual force-fetch from users. > [1] <a href="https://lists.freedesktop.org/archives/mesa-dev/2015-June/087904.html">https://lists.freedesktop.org/archives/mesa-dev/2015-June/087904.html</a> Oh, interesting. I guess we could mostly wait it out: keep the tags on fd.o, and just not bother pushing them to GitHub. Deleting most of the r300 tags (red_tinted_cube) is probably sensible anyway, as I don't imagine anyone would want them ...</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>