David A. Greene
greened at obbligato.org
Thu Jul 28 16:11:14 PDT 2011
Óscar Fuentes <ofv at wanadoo.es> writes:
> Bob Wilson <bob.wilson at apple.com> writes:
>> Sorry, but I have no idea what you're talking about. I use git
>> exclusively for all my llvm development, and I make extensive use of
>> branches and merging. I haven't had any problems related to git-svn.
> Exactly, you have no idea what he is talking about :-)
> The problem with git-svn is that once a revision is sent from git to
> svn, it comes back with a different identity (revision-id) so for git it
> is a new reivision. That's a PITA (or rebase hell, to be more
> descriptive) if you have branches containing the original revisions plus
> some others on top of them and later you want to merge svn's mainline
> into them. Variations of that scenario are to be expected on a team that
> contributes chunks of changes upstream but keep other changes internally
> or in development phase.
Ding! ding! ding! ding! ding!
git-svn is better than svn but it is still short of git proper.
More information about the llvm-dev