On Tue, May 14, 2013 at 4:18 PM, Junio C Hamano <gits...@pobox.com> wrote:
> Felipe Contreras <felipe.contre...@gmail.com> writes:
>> I forgot to mention the main objective of the shared repo feature:
>> + first/
>> * first/second/foo
>> * first/third/foo
>> * first/fourth/foo
>> * first/fifth/foo
>> * first/sixth/foo
>> Since in bazaar branches are repositories, we want to make it possible
>> for remote-bzr users to create a single remote per branch as easily as
>> possible (without having to duplicate huge clones).
>> But as I said, without this patch, they wouldn't be able to use that
>> feature if they cloned with v1.8.2.
> So we nuke that and have them clone from scratch? I am not saying
> that is bad. I just want us to be honest about the implications
> when including it in the ReleaseNotes.
The user won't have to do a thing, it happens behind the curtain.
And the clone would happen either way, with or without this patch,
because 'hg/origin/master' doesn't exist, the only purpose 'hg/origin'
serves is to block the new feature.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html