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

Re: need help with syncing two bare repos

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 3, 2012, 20:00 UTC
Message-ID
<7vboirbva3.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CAPZPVFax6wa9QYOMxghhWK6LJaYWS2+WCbWQLA+LE53TdNXJhQ@mail.gmail.com>
Eugene Sajine <euguess@gmail.com> writes:
> I think the best variant would be to do something like:
>
> $ git pull --rebase /refs/heads/*:/refs/heads/*
> $ git push origin /refs/heads/*:/refs/heads/*

You perhaps meant "worst" not "best" here. From the point of view of people who have pushed into the "origin" repository we see above, their history is rewritten; you are screwing half the population by doing this.

Not allowing B to accept pushes while it is not positively sure that A has gone down would of course be the best solution (in your scenario, B started serving when it merely found out that *it* cannot contact A), but barring that, the recovery for two histories at A and B, once they diverged, should be to "merge" corresponding branches.

Previous: Sitaram ChamartyNext: Eugene Sajine
Message 3 of 5 in “need help with syncing two bare repos”
  1. Eugene SajineAug 3, 2012
  2. Sitaram ChamartyAug 3, 2012
  3. Junio C HamanoAug 3, 2012
  4. Eugene SajineAug 3, 2012
  5. Junio C HamanoAug 3, 2012

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.