From: Richard Purdie <rpurdie@rpsys.net>
To: Git Mailing List <git@vger.kernel.org>
Subject: git pull fails with http urls?
Date: Tue, 04 Sep 2007 15:10:53 +0100 [thread overview]
Message-ID: <1188915053.5705.12.camel@localhost.localdomain> (raw)
I've noticed a problem with pulling http urls. I can clone them fine:
git clone http://www.gnome.org/~alexl/git/gio.git/
and I can pull with:
git pull
which works as expected however if I try:
git pull http://www.gnome.org/~alexl/git/gio.git/
it fails with:
error: pick-rref: HEAD not found
No such ref HEAD at http://www.gnome.org/~alexl/git/gio.git/
The HEAD file is there at http://www.gnome.org/~alexl/git/gio.git/HEAD
and:
git pull http://www.gnome.org/~alexl/git/gio.git/ master
works. It seems git just doesn't want to see/understand the HEAD file?
Is the above supposed to work or is something wrong with the above
commands? I see this with git 1.5.2.3 and 1.5.3, google suggests this
might have worked with 1.4.x and broke in 1.5...
Regards,
Richard
next reply other threads:[~2007-09-04 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-04 14:10 Richard Purdie [this message]
2007-09-04 19:17 ` git pull fails with http urls? Junio C Hamano
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=1188915053.5705.12.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--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 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).