On Wed, 2009-03-18 at 11:09 +0100, Dierk König wrote:
[ . . . ]
> Well, not sure what "interwork" means but git is able to sync with svn -
> but that process is slow and needs additional work for every "push"
> (if you don't use a commit hook, but that raises other issues...).
The question is whether you want the Subversion repository to be
actively used as part of the development workflow or whether it is just
going to be a repository kept, read-only, as an historical record. In
the latter case developers do not use Subversion ever and almost any
arrangement is possible.
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.
As noted previously Bazaar can behave as Git does as a Subversion
client, but it can also write a Bazaar branch into the Subversion
repository -- making them peers. This means the Subversion repository
is just another place for storing Bazaar branches and DVCS is possible.
And people can still use Subversion if they have to.
> I would say that rebase is cool as long as you're working locally. As
> soon as
> any affected commit is published, it becomes dangerous - no matter
> what the public repo is
> (git or svn). Not sure about hg and bzr in this respect.
Exactly. Though I would not say dangerous, I would say that it breaks
the relationship with other previously related branches and
repositories.
> >
> > On this issue Bazaar is the only choice.
>
> As soon as we move to a DVCS, I would delete the svn repo. Honestly!
Codehaus seem to be moving on geological timescales on this issue :-(
--
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:russel.win...@ekiga.net
London SW11 1EN, UK. m: +44 7770 465 077 xmpp: rus...@russel.org.uk
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
