All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Oliver Kullmann <O.Kullmann@swansea.ac.uk>
Cc: git@vger.kernel.org
Subject: Re: how to use two bare repositories?
Date: Fri, 11 Apr 2008 17:12:38 -0700	[thread overview]
Message-ID: <7vabk0nd6x.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080411234430.GQ29940@cs-wsok.swansea.ac.uk> (Oliver Kullmann's message of "Sat, 12 Apr 2008 00:44:30 +0100")

Oliver Kullmann <O.Kullmann@swansea.ac.uk> writes:

>> > 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.

  reply	other threads:[~2008-04-12  0:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-11 23:44 how to use two bare repositories? Oliver Kullmann
2008-04-12  0:12 ` Junio C Hamano [this message]
2008-04-12  0:42   ` しらいしななこ
2008-04-12  0:55     ` Junio C Hamano
  -- strict thread matches above, loose matches on Subject: below --
2008-04-11 22:22 Oliver Kullmann
2008-04-11 23:17 ` Junio C Hamano
2008-04-11 23:19 ` Jean-Luc Herren
2008-04-11 23:23 ` Oliver Kullmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vabk0nd6x.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=O.Kullmann@swansea.ac.uk \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.