Hi,
I have switched to git just two days ago, and i am quite happy about it.
Although i do not want hadoop to move to git before apache
infrastructure have matured enough. As Linus addresses in his talk, many
users have been using git+svn in a very innovative way. The central
repository is managed by svn and the users checkout the code, build a
local git repo and work from there. Personally i find it *very*
convenient to let both svn and git manage the code. What i do is make
git ignore svn files, and make svn ignore git files. Then i just branch
once for every issue i work on. Committing the changes before switching
to the other branch(issue). After I've done with the issue i get the
patch with regular svn diff. Anyhow i am telling about this because it
enabled me to work on several distinct issues simultaneously using the
same code base. I highly suggest this workspace-model to anyone working
this way.
Jeff Hammerbacher wrote:
hey all,
so we're starting to really use hadoop heavily here at facebook, and we'd
like to start contributing back to the hadoop trunk. we've been through
this process before (contributing heavily to an actively developed open
source project) with memached, and the guy who owns the trunk of that
project is quite the SCM nut who says that his life has been made infinitely
more pleasant by switching from svn to git for version control with
memcached.
i'm not suggesting the project be moved tomorrow. i just wanted to throw
the question out there to get a sense of how others feel about git as an SCM
tool. i have asked our memcached guy to write up the specific advantages of
git versus svn so i will be happy to follow up with details.
apologies if this has been brought up before; i've been reading the mailing
list on and off now for several months and a quick search of the archives
yielded no matches for "git" so hopefully this is a relevant topic.
thanks,
jeff
