{"thread":{"id":"3639","subject":"Direct CVS import tool","startedAt":"2006-03-13T08:25:42Z","lastAt":"2006-03-13T08:25:42Z","messageCount":1,"participants":["Keith Packard"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"17516","messageId":"1142238342.24217.63.camel@neko.keithp.com","threadId":"3639","inReplyTo":null,"subject":"Direct CVS import tool","fromName":"Keith Packard","fromEmail":"keithp@keithp.com","sentAt":"2006-03-13T08:25:42Z","receivedAt":"2006-03-13T08:25:42Z","isPatch":false,"sender":{"key":"keithp@keithp.com","avatar":"https://gravatar.com/avatar/fa1f479cdd51322fe86215c955a81d296bbf66a1fe625f8a12d87a8ec7faf648?d=mp&s=160"},"body":"I've got some rather large, broken, CVS trees that I'm trying to migrate\nto git (X.org).\n\nAttempts to do this with the existing cvsps-based git-cvsimport have\nproved rather disasterous; missing files, incorrect log messages and\nincorrect revisions are spread throughout the tree, including on the tip\nof each branch.\n\nI'm reasonably sure the problems are caused by cvsps, and while I've\nhacked at that quite a bit, it seems like it's so focused on analysing\nthe tree for putative software engineering reesarch that it cannot be\nmade to accurately reproduce the tree via changeset analysis.\n\nSo, I've given up hacking cvsps and wrote a simple RCS file parser that\ndirectly reads ,v files into a git-like revlist structure, and then\nmerges those together into a final tree. At this point, it's generating\nthe right head information for every named branch, but it's still not\nsuccessfully connecting all of the branches back together at suitable\npoints.\n\nIt's also not yet generating actual git trees; instead it dumps the\ngenerated revision tree structure to a graphviz file for visual\ninspection of the results.\n\nBut, I figured instead of doing this work in secret, I'd let people know\nwhat I'm up to in case others want to play along.\n\ngit://git.freedesktop.org/~keithp/parsecvs\n\nAnd, of course ideas for a suitable name would be welcome.\n\n-- \nkeith.packard@intel.com\n"}]}