Re: [PATCH] remote-hg: add shared repo upgrade

From: Antoine Pelisse <apelisse@gmail.com>
Date: Aug 5, 2013, 19:54 UTC
Message-ID: <CALWbr2zzepjoBEcPYGoqPs9ro0fk_wNWYCE2ZGhW-FY4Gz8gWQ@mail.gmail.com>
In-Reply-To: <CAMP44s0Wsnqs_t5kJb0Le13MrzN9WNRTrtNEuXHrDU6D7AKjLg@mail.gmail.com>

On Mon, Aug 5, 2013 at 9:31 PM, Felipe Contreras <felipe.contreras@gmail.com> wrote:

Show 16 quoted lines

> On Mon, Aug 5, 2013 at 2:22 PM, Antoine Pelisse <apelisse@gmail.com> wrote:
>> From: Felipe Contreras <felipe.contreras@gmail.com>
>>
>> 6796d49 (remote-hg: use a shared repository store) introduced a bug by
>> making the shared repository '.git/hg', which is already used before
>> that patch, so clones that happened before that patch, fail after that
>> patch, because there's no shared Mercurial repo.
>>
>> It's trivial to upgrade to the new organization by copying the Mercurial
>> repo from one of the remotes (e.g. 'origin'), so let's do so.
>
> In addition to that, simplify the shared repo initialization; if the
> repository is shared, the pull on the child will use the parent's
> storage, so there's no need for the initial clone.
>
> And make sure the shared repository is always present.

It comes without saying that you can change this description if you want to :-)

> It seems pretty clear to me that we are talking about multiple patches here.

I'm not sure that's necessary. But I may be missing something.