Benchmark: Git 1.6.3.3, Hg 1.3.1, Bzr 1.17

[John Szakmeister]

On Mon, Aug 17, 2009 at 8:16 PM, Andrew
Cowie<andrew at operationaldynamics.com> wrote:
> On Tue, 2009-08-18 at 00:18 +0300, Jari Aalto wrote:
>
>> Yes, that was typical "full clone" scenario.
>
> Except that we know it's not typical, right?

Just out of curiosity, how do we know that?  I've avoided them in my
environment because we have a workspace of 7 different repos being
brought together.  So when I branch, it tends to be a "full clone".
:-(

[snip]
> So long as casual users can "misuse" bzr, they will, and bzr will look
> bad as a result. Which is why I think fundamentally changing this is so
> important. I had hoped it could have been addressed before declaring
> 1.0. Ah, naiveté.

I couldn't agree more.

[snip]
> For what it's worth, I do my best to counter-act this problem by
> encouraging people to set things up "properly" from the get-go, for
> example with these instructions
> http://java-gnome.sourceforge.net/4.0/HACKING.html
> but only rarely do people actually know of or follow the recipe (let
> alone following it all the way to having a switched Eclipse project).
> Which leaves me constantly having to attempt to remotely debug other
> people's borked checkouts & branches & setups of our project, which is
> not fun, and makes for a lovely first impression of Bazaar for people.

That's disappointing. :-(  But thanks for taking the time to write
that down... seems like a good place to start for others as well.
Perhaps we can fold that into some Bazaar docs so other projects have
a nice template to get them started?

-John