As part of that learning curve, make sure you check out gitx (on the mac, gitg on linux, I don't care what is on windows).
It makes it easier to understand what the branching structure is. I recommend invoking as gitx --all to show all of the branches right away. This will highlight the interesting ability of git to stage and commit individual lines of changes rather than entire files full of changes as with svn. That can be really handy if you want to document the changes more precisely. That precision, in turn, can make merges easier. On Sun, Sep 18, 2011 at 2:18 PM, Grant Ingersoll <gsing...@apache.org>wrote: > > On Sep 18, 2011, at 3:20 PM, Ted Dunning wrote: > > > Actually, this is important to say. Speed is one of the huge advantages > of > > git over other options. > > That is, once you are over the learning curve and have a good workflow! > I've been doing an SVN patch workflow for a long time now and it has served > me well. Oh well, time to move on! > > > > > On Sun, Sep 18, 2011 at 1:13 PM, Dawid Weiss > > <dawid.we...@cs.put.poznan.pl>wrote: > > > >> In case of Lucene you can also work on multiple svn branches and do > >> the switching using git... needless to say this is way faster than > >> using svn. > >> > >
