On Mon, 2008-06-30 at 21:19 +0200, Jochen Theodorou wrote:

> Can I take this as that I can simply use bazaar locally, without 
> changing svn and then commit to svn, whenever I like to do so and 
> without somebody seeing I actually did it using bazaar? I mean if it is 
> like this, then we could for now switch to wahtever can work with the 
> subversion backend unmodified and let the individual developer decide 
> what to take. We could then still switch to another repository system later

You can do this with either Bazaar or Git.  From what Jim says you can
do this with Mercurial as well -- I will check this out later in the
week.

Because I prefer Bazaar over Git, I have created Bazaar branches for
Groovy and Gant and am maintaining them on Launchpad.  This is actually
more of a Groovy and Gant marketing exercise than anything else.  But
what it does mean is that people have a branch they can go to to start
using Bazaar as their Subversion client without the hassle of having to
wait a long time for the generation of their own branch direct out of
Subversion.

Perhaps there is also an argument for hosting the Git repository
somewhere as well.

The dpush command for Bazaar is only available in the bzr-svn 0.4.11
beta using bzr 1.6 beta, but both should be released very soon now.
Using push to a Subversion repository means the metadata for the Bazaar
branch is added to the Subversion repository, dpush does not do this.
If the Codehaus Subversion commit hook didn't list all property changes
then there wouldn't be an issue but Ben doesn't have the time to
investigate switching from using svnlook to using the Python mail hook.
I use the Python mail hook for my Subversion repositories and so I don't
see the problem that I mention previously and caused Chanwit to switch
to Git as his Subversion client.  The dpush command makes all the
Codehaus commit hook hassle go away in the same way the using git svn
dcommit does.

> > Yes, Git is still a little faster (well quite a lot is some cases), but
> > Bazaar is so much easier to use.
> 
> Well, Git might be faster.. but how much? If there is not a bazaar 
> operation that takes 10 minutes with it but only 1 with git, then there 
> is probably not much to talk about. Or are there operations with 
> different complexitiy?

It depends on the command.  For basic commit, diff, etc. Git is faster
than Bazaar but you wouldn't worry about it as they are both fast
enough.  For some log operation Git is very much faster than Bazaar and
so you would care.  For some push and pull operations, Git can be a lot
faster than Bazaar, but in the main they are both fast enough not to
care about the difference.  I suspect Mercurial sits between Git and
Bazaar in all cases.

For me the issues are that the speed issues are not generally an issue,
i.e. the extra speed of Git does not offset my preference for the branch
model of Bazaar compared to Git, and the command line command set.  And
I much prefer olive-gtk (the GTK bazaar GUI) to the Git equivalents.
Except there is one thing about gitk that is really cool, and I have a
feature request in to have that added to the equivalent Bazaar tool.

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

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