From: Junio C Hamano <junkio@cox.net>
To: Theodore Tso <tytso@mit.edu>
Cc: "Santi Béjar" <sbejar@gmail.com>, git@vger.kernel.org
Subject: Re: git-receive-pack doesn't understand objects/info/alternates?
Date: Mon, 16 Apr 2007 10:34:18 -0700 [thread overview]
Message-ID: <7v3b30usth.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20070416153040.GG27533@thunk.org> (Theodore Tso's message of "Mon, 16 Apr 2007 11:30:40 -0400")
Theodore Tso <tytso@mit.edu> writes:
> 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.
next prev parent reply other threads:[~2007-04-16 17:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-16 12:22 git-receive-pack doesn't understand objects/info/alternates? Theodore Ts'o
2007-04-16 13:13 ` Santi Béjar
2007-04-16 15:30 ` Theodore Tso
2007-04-16 17:34 ` Junio C Hamano [this message]
2007-04-16 18:48 ` Theodore Tso
2007-04-16 18:57 ` Linus Torvalds
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=7v3b30usth.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=sbejar@gmail.com \
--cc=tytso@mit.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).