Hi Andrew, On 11-04-12 00:57, Andrew Sayers wrote: > Would I be right in thinking that a commit like "Merged r100,r101,r102 > from trunk" will create three grafts? If so, that might be the problem. One SVN 'merge' commit will generate one graft. The graft itself will contain all revisions mentioned in the merge commit, and whatever the original git parent was before the graft. > Git differentiates between "merges" (which include every commit up to > and including the specified one) and "cherry-picks" (which just include > the specified commit), whereas SVN calls both of these "merges". Grafts > are a way of creating "merges" rather than "cherry-picks" (which git > doesn't have any metadata for), and it's not at all easy to get "merge" > data out of SVN in the general case. Having said that, it's often a > good enough heuristic to pick the highest revision number mentioned in > the commit message and pretend it's a merge. The way we 'merged' in SVN was indeed more like cherry-picking, but I'm looking to display this information as a merge in Git. I also would like to include all revisions if possible. The real problem I seem to be having is not completely understanding how Git grafts work, because I think I'm hitting some kind of limitation or bug, or just not using it right. > Incidentally, I'm planning to work on this area of SVN->git conversion > in the coming months. I don't have anything you could use yet, but I > don't suppose the scripts you used are available somewhere? Getting > revision information out of log files is particularly tricky, and > everyone stumbles over a different set of issues. I'd be really > interested to pick any nuggets of wisdom out of the approach you took. I don't really have any useful script for you at the moment, but the main approach is this: * I first tag all SVN Git commits with the original SVN revision, like: "svn/1234" * Then I retrieve all commits with "merge" in the message, but not "unmerge" * Now I filter all revisions from the commit message using a regex or two. * Using all relevant revisions, I retrieve the corresponding SHA hashes using the tag names I created in step 1. * Finally, I write a graft file in format: <merge commit> <original git parent> <merge rev 1> ... <merge rev n> Kind regards, Nick Douma
Attachment:
signature.asc
Description: OpenPGP digital signature