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

Re: how to use two bare repositories?

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 12, 2008, 00:12 UTC
Message-ID
<7vabk0nd6x.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<20080411234430.GQ29940@cs-wsok.swansea.ac.uk>
Oliver Kullmann <O.Kullmann@swansea.ac.uk> writes:
Show 15 quoted lines
>> > The problem is now that it seems not to be possible
>> > to update B:
>> >
>> > 1. pulling from A is not possible since B is bare;
>> > 2. fetching from A seems to work, checking the content of
>> >    B via gitk seems to indicate that B has been updated
>> >  --- however pulling from B doesn't work
>> 
>> The usual answer when you see a word "http" mentioned is...
>> 
>> 	how are you arranging update-server-info to be run whenever B is
>> 	updated?
>
> Aha, I see: So first I fetch, and then I run update-server-info.
> Just tried it out, and it worked. Thanks!

Typically, you would update a bare repository used for publishing by pushing into it, and trigger update-server-info from the post-update hook.

But it is perfectly fine if you initiate a mirror-fetch from that publishing repository (in your case, "B"), and the caller to "git fetch" can run update-server-info after fetching.

And no, there is not a "post-fetch" hook, nor is there a need for one.
Previous: Oliver KullmannNext: しらいしななこ
Message 2 of 4 in “Re: how to use two bare repositories?”
  1. Oliver KullmannApr 11, 2008
  2. Junio C HamanoApr 12, 2008
  3. しらいしななこApr 12, 2008
  4. Junio C HamanoApr 12, 2008

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.