git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Felipe Contreras <felipe.contreras@gmail.com>
Date
Aug 5, 2013, 19:31 UTC
Message-ID
<CAMP44s0Wsnqs_t5kJb0Le13MrzN9WNRTrtNEuXHrDU6D7AKjLg@mail.gmail.com>
In-Reply-To
<1375730567-3240-1-git-send-email-apelisse@gmail.com>
On Mon, Aug 5, 2013 at 2:22 PM, Antoine Pelisse <apelisse@gmail.com> wrote:
Show 9 quoted lines
> 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 seems pretty clear to me that we are talking about multiple patches here.
-- 
Felipe Contreras
Previous: Antoine PelisseNext: Antoine Pelisse
Message 2 of 8 in “remote-hg: add shared repo upgrade”
  1. remote-hg: add shared repo upgradeAntoine Pelisse, Aug 5, 2013
  2. Felipe ContrerasAug 5, 2013
  3. Antoine PelisseAug 5, 2013
  4. Junio C HamanoAug 5, 2013
  5. Antoine PelisseAug 6, 2013
  6. Junio C HamanoAug 6, 2013
  7. Antoine PelisseAug 6, 2013
  8. 1/2 remote-hg: add shared repo upgradeAntoine Pelisse, Aug 9, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.