Re: git-receive-pack doesn't understand objects/info/alternates?

From: Junio C Hamano <junkio@cox.net>
Date: Apr 16, 2007, 17:34 UTC
Message-ID: <7v3b30usth.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <20070416153040.GG27533@thunk.org>

Theodore Tso <tytso@mit.edu> writes:

Show 18 quoted lines

> On Mon, Apr 16, 2007 at 03:13:25PM +0200, Santi Béjar wrote:
>> On 4/16/07, Theodore Ts'o <tytso@mit.edu> wrote:
>> >
>> >When I push a kernel repository to master.kernel.org, where the
>> >repository only has at most a dozen changes on top of 2.6.21-rc7, I
>> >noticed that it tried to push a *lot* of objects over ssh.  As in:
>> 
>> This is because git only trusts the the commits in $GIT_DIR/refs.
>> Since commit v1.5.1-107-ge3c6f24 (in next) git-fetch first checks if
>> we have all the objects that we are going to fetch available locally.
>> This could be added for the push. But for now you could add a branch
>> in your repo in master.kernel.org to track linus' master branch.
>
> Thanks for the explanation!  
>
> So if I add a symlink from .git/refs/heads/kludge to
> <linus'-tree-on-master>/.git/refs/heads/master this should work as a
> workaround now, right?

Theoretically speaking, not necessarily. Practically speaking it perhaps may.

When Linus runs 'pack-refs --prune', your kludge symlink would not be of any help, as the command removes everything under his linux-2.6.git/refs directory and records the equivalent information in linux-2.6.git/packed-refs file.

        Word of caution.  Symlinking his packed-refs file to
        your repository would not work either.