Dirk-Willem van Gulik wrote:
> Ross Gardler wrote:
> > I understand that GiT can be used locally as a layer on top of SVN.
> > I believe this gives you most of the perceived benefits of GiT
> > locally without the need for a project itself to switch to GiT.
The issue isn't git as an SVN client. No one (as far as I know) cares what
SVN client(s) you use, so long as they don't abuse our SVN server.
> I am a bit lost here as well -- what does GiT add to the processes/
> workflows common in the ASF ?
> One of the great things about GiT is that you can can have lots of
> parallel and non-linear merges (every developer their own branch;
> However in the ASF most groups work roughly along fairly linear lines;
> with 'one' or just a 'few' points at which a patch is accepted - and
> essentially few, or just one, merge point (or a single line of merge
> points when backported). Rarely do we merge multiple 'HEAD's.
And most importantly, we want our development to be visible to the
Community, not done in private and committed when finished. Developers can
always make more or less transient branches to work on code, still in public
view, and merge back to shared locations. The key point here that I believe
you, I, William and others are all making isn't about technology, it is
about practice.
Now, if there is an SCM that substantially improves the ASF's ability to
perform *our* practices, that is a separate discussion item.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
