Pushing relative subrepos

[Georg Zetzsche]

Am 18.11.2010 18:27, schrieb Matt Mackall:
>>> No. It's always been the user's job to initialize repositories before
>>> pushing to them.
>>
>> Keeping this behaviour would mean that every time someone adds a subrepo
>> (which I would consider part of the parent repo, if it has a relative
>> location), they have to ask an administrator to initialize a subrepo with
>> the corresponding name, although they have the permission to push. Is this
>> really the intended workflow?
> 
> No, actually, the intended workflow in a distributed system is for
> everyone to have admin rights on their own private publishing repos, and
> to never push to shared repositories. But people still recovering from
> CVS seem to like having everyone still race to push to a single shared
> repository. That's allowed, but it's not optimal.

OK, but then you still have to replicate every new subrepo (that you
created yourself or received through other pulls) manually when you
push to your private publishing repo. I just thought "replicating
changes" is something a VCS should take care of. But I don't see a
way around it.