On Thu, 2009-03-19 at 10:42 +0100, Marcus Better wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Russel Winder wrote:
> > If the Subversion repository is active then Git can be used as a client
> > -- but only on an individual basis since committing to the Subversion
> > repository requires a rebase which alters the history stored in the Git
> > repository.
> 
> It might be added that developers can clone a public git mirror and then 
> pull changes in the svn-tracking branches either from there or directly from 
> svn, and git-svn will do the right thing.

Absolutely right.  And this can be the same with Bazaar.

The point is that if Git is the Subversion client of choice then there
is a very specific star workflow that must be enforced if the Subversion
repository is active, indeed the Subversion repository has to be the
mainline in this case.

This workflow is also possible with Bazaar, but Bazaar also allows the
normal DVCS workflow even where one of the branches is actually held in
a Subversion repository.

If git-svn were to evolve to do (functionally) what bzr-svn does then
Git could do what Bazaar currently does.  I don't know if anyone is
working on this.  I suspect not because the seemingly prevalent Git mind
set is to treat a Subversion store as a second class citizen.

The important point I have been banging on about is that normal DVCS
workflows are possible with Bazaar even where the mainline is a
Subversion repository, but that normal DVCS workflows are not possible
currently with Git if the Subversion repository is an active peer.

Take Subversion out of the equation and all the metrics change.
Codehaus is though a Subversion only organization -- at least for the
foreseeable future.

-- 
Russel.
============================================================
Dr Russel Winder                 Partner

Concertant LLP          t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road,     f: +44 8700 516 084    voip:  
sip:[email protected]
London SW11 1EN, UK.    m: +44 7770 465 077    xmpp: [email protected]

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to