BDFL decision of Python's DVCS

[Andrew Bennetts]

David Cournapeau wrote:
[...]
> etc... Same for reviews. The UI for this is simply not there in bzr ATM.
> Git really IS simpler than bzr (and maybe hg ?) for this. And git IS
> less confusing because it does not use revno. How bzr can be used for
> the following ?
> 
> git log foo_1.1  foo_1.2

I'm not sure exactly what this means, e.g. in bzr's various release branches
are diverged from each other so there's no obvious log of a single line of
development between the 1.1 branch and the 1.2 branch.

However, "cd foo_1.1; bzr missing ../foo_1.2" might be close.

> git diff foo_1.1  foo_1.2

This one is easy:

$ bzr diff --old bzr-1.12/ --new bzr-1.13 | diffstat | tail -1
 454 files changed, 15333 insertions(+), 6543 deletions(-)

> Given that this works for remote branches as well - where it can

The arguments you can give to --old and --new can be URLs to remote branches.

> potentially be very useful for review (I say potentially because I have
> yet used this workflow with 'real' git, only with git-svn, which
> complicated the matter a lot).

Although “bzr merge --preview OTHER”, “bzr diff -rancestor:OTHER” or even “bzr
send” are probably more common ways to do reviews in bzr than direct diffs.  It
depends on what exactly you want to review.

[...]
> I hope that once bzr is fast enough, discussion will move on the the
> *interesting* problems and potentials of DVCS.

I hope so too!

-Andrew.