On Wed, Nov 12, 2008 at 07:00:03PM +0000, Martin Stjernholm, Roxen IS @ Pike developers forum wrote: > developing e.g. the multicore support, since the initial development > can take place on a separate branch without upsetting the main tree > and then rebased and merged with it without losing the history
if you use git you would not loose the history anyways. why do you want a rebase? there is no problem to do the development with git and then rebase, and after that commit to svn though. you could even take an svn branch, check it out with git and use git to rebase it, then git-svn to commit it back. (bill, sorry for my last comment, i think this is what you meant. it's not a feature of git-svn however, but of git itself. i try to avoid using git-svn as much as possible though, only git-svn fetch and git-svn dcommit) > (i.e. it all won't become a gigantic commit with a single laconic > message like "Multicore support."). Afaik svn doesn't handle that, but > maybe I'm wrong? i don't understand what's wrong with a merge commit? it would point to two branches (in git now, but i think also in svn with the merge tracking in 1.5) that said, i am definetly in favour of using git :-) git-svn is nice as far as svn is concerned but not as good as it could be from a git perspective.
