On Tuesday 16 March 2010 14:12:20 Mark Miller wrote: > On 03/16/2010 09:05 AM, Andrzej Bialecki wrote: > > > > You could have used git instead. There is a good integration > > between git and svn, and it's much easier (a giant > > understatement...) to handle branching and merging in git, both > > between git branches and syncing with external svn. > > Yeah, we have actually discussed doing things like GIT in the past - > prob main reason we didn't is learning curve at the moment. I haven't > used it yet.
I jumped off perforce by using a git-perforce bridge for daily work. This made me comfortable with git while not changing anything public. And I had the certainty that if anything goes wrong, I can do it in perforce. Meanwhile we migrated a 2GB trunk sources repo from a legacy repo to git and it works fine. So don't hesitate do use a git-svn bridge. git will open new modes of operation, e.g. instead of up- and downloading patches in jira just hold a branch for any patch in a repo, which is as public as jira, batch-upgrade that branches/patches to trunk and pull that branches into the core developers repo as desired. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
