BDFL decision of Python's DVCS

[Matthieu Moy]

Jurgen Defurne <jurgen.defurne at pandora.be> writes:

> Looking at other VCS's, notably git and Hg, it did not seem that they
> delivered other features I need. E.g. I can set up a central
> repository for bzr which can contain all nested trees,

You'd have to set up one branch per sub-project, I guess. If you want,
you can create a shared repository, but if the sub-projects do not
share revisions, a shared repository won't really share anything.

> but for git you can only set up one central branch and as far as I
> found, all other 46 components need to be different branches.

Well, if they are subdirectories, they'll be in the same project, but
if you actually do subprojects, I don't understand how you'd want to
put them in the same "branch" (well, probably we don't call "branch"
the same thing). Now, Git has a notion of submodules, and a notion of
subtree merge (that allows you to manage subsystems in separate
branches while keeping the complete work-tree in a branch).

> In Hg I haven't even found evidence or documentation that there was
> something available like nested trees or svn:externals.

?

Both of

http://www.google.com/search?q=mercurial+subproject
http://www.google.com/search?q=mercurial+svn%3Aexternals

would have pointed you to the forest extension as a first result.

-- 
Matthieu