Pushing relative subrepos

[Georg Zetzsche]

Am 18.11.2010 12:20, schrieb Georg Zetzsche:
> Am 17.11.2010 21:32, schrieb Matt Mackall:
>>> As far as I can see, "hg push" should "hg init" a subfolder in the
>>> target repo before pushing the subrepo in this case.
>>>
>>> Is this a bug?
>>
>> 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?
> 
> On the other hand, when you pull -u from a repo that has a new subrepo,
> a new folder is readily initialized. Isn't this somewhat asymmetrical?

Sorry, I just realized that initializing new subrepos means to modify the
workdir (even regardless of which revision is currently checked out), which
push really should not do.

Then I guess the cumbersome creation of subrepos in a pushable repo is the
only way to go. Or is there an alternative?