From: Junio C Hamano <junkio@cox.net>
Date: Tue, 13 Sep 2005 22:29:07 GMT
Subject: Re: dumb transports not being welcomed..
Message-ID: <7v7jdkwqj0.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <432750E1.3020508@pobox.com>

Jeff Garzik <jgarzik@pobox.com> writes:

> Junio C Hamano wrote:
>> The file $GIT_DIR/info/refs was introduced to solve this by
>> listing the available refs for discovery, and hooks/post-update,
>> when enabled, runs update-server-info to update the file (among
>> other things) whenever you push into the repository.
>
> This is helpful.  I'll run git-update-server-info before each push, now.

Just to make sure I am not misunderstanding you, is your "publish"
workflow like this?

    - do your work on your private machine
    - git-update-server-info in your private repository
    - rsync that out to master.kernel.org

If so, then "before each push" makes sense.  

I know you understand the following but this is for other people
on the list.

The hooks/post-update I was talking about assumes a different
"publish" workflow:

    - do your work on your private machine
    - git push master.kernel.org:/pub/scm/...

and you have hooks/post-update enabled in the repository on
master.kernel.org; the counterpart program for 'git push' which
runs on master.kernel.org updates the info/refs and objects/info/packs
file over there once your push is done.