From: Junio C Hamano <gitster@pobox.com>
To: Richard Purdie <rpurdie@rpsys.net>
Cc: Git Mailing List <git@vger.kernel.org>
Cc: Petr Baudis <pasky@suse.cz>
Subject: Re: git pull fails with http urls?
Date: Tue, 04 Sep 2007 12:17:06 -0700 [thread overview]
Message-ID: <7vsl5umea5.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1188915053.5705.12.camel@localhost.localdomain> (Richard Purdie's message of "Tue, 04 Sep 2007 15:10:53 +0100")
Pasky seems to have a locally modified version at repo.or.cz to
add HEAD to the result of update-server-info, but as far as I
can see, update-server-info never placed HEAD in the result, and
I do not think ls-remote compensated it by adding HEAD by hand,
so that change is fixing the symptom rather than fixing the
regression, but I am not sure where the true regression is.
Most likely we broke git-fetch while trying to deal with
repositories with insanely large number of refs (aka
"fetch--tool partial rewrite in C").
Having said all that, I think it is a good idea nevertheless to
add HEAD information across all transports, like Pasky's patch
does. Currently http/ftp/rsync do not report HEAD while git
native protocols do.
Pasky, care to submit "server-info: Add HEAD to info/refs" for
inclusion?
prev parent reply other threads:[~2007-09-04 19:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-04 14:10 git pull fails with http urls? Richard Purdie
2007-09-04 19:17 ` Junio C Hamano [this message]
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=7vsl5umea5.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=rpurdie@rpsys.net \
/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).