James Y Knight via llvm-dev
2018-Nov-06 14:59 UTC
[llvm-dev] New LLVM git repository conversion prototype
I've regenerated the repository set at https://github.com/jyknight/llvm-git-migration again, with these fixes. James, could you prune r70891? It cuts the history. Done. On Tue, Oct 23, 2018 at 2:44 PM James Y Knight <jyknight at google.com> wrote:> My preference is "all or nothing" :) >> > > Yes, I think it's probably best to preserve the empty directory add+modify > commits. I'll fix this... >Done. 2) Glitches of authors who have changed their name>> >> I found too many commits that have incompatible author filed. >> I heard from you, you have sought through commits, mailing lists. >> But I don't think all of glitches would be intentional. >> > > Indeed -- oops! I managed to insert an off-by-one error into the author > mapping function, so there's a mismatch at every revision where the mapping > changes. Fixing that... >Done, and double-checked again against the old git conversion. I also took the opportunity to add some more fixups for CVS issues back to the 1.0 release. I've now also now verified that the file moving done by these CVS fixes didn't end up accidentally losing changes, by iterating over all the commits and ensuring that file hashes in a recursive ls-tree have not disappeared from the commit (just changed their path). -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20181106/1e57c1b1/attachment.html>
NAKAMURA Takumi via llvm-dev
2018-Nov-06 21:51 UTC
[llvm-dev] New LLVM git repository conversion prototype
James, thanks for working. As far as I have checked through trunk, there is no major problem. I saw a few differences in author name, but I assume they would be intentional, since you say you double-checked :) I haven't checked branches yet, but I think we can easily rewind branches at the moment. Takumi On Wed, Nov 7, 2018 at 12:00 AM James Y Knight <jyknight at google.com> wrote:> I've regenerated the repository set at > https://github.com/jyknight/llvm-git-migration again, with these fixes. > > James, could you prune r70891? It cuts the history. > > > Done. > > On Tue, Oct 23, 2018 at 2:44 PM James Y Knight <jyknight at google.com> > wrote: > >> My preference is "all or nothing" :) >>> >> >> Yes, I think it's probably best to preserve the empty directory >> add+modify commits. I'll fix this... >> > > Done. > > 2) Glitches of authors who have changed their name >>> >>> I found too many commits that have incompatible author filed. >>> I heard from you, you have sought through commits, mailing lists. >>> But I don't think all of glitches would be intentional. >>> >> >> Indeed -- oops! I managed to insert an off-by-one error into the author >> mapping function, so there's a mismatch at every revision where the mapping >> changes. Fixing that... >> > > Done, and double-checked again against the old git conversion. > > I also took the opportunity to add some more fixups for CVS issues back to > the 1.0 release. I've now also now verified that the file moving done by > these CVS fixes didn't end up accidentally losing changes, by iterating > over all the commits and ensuring that file hashes in a recursive ls-tree > have not disappeared from the commit (just changed their path). > > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20181107/e3e1fdac/attachment.html>