git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Mike Hommey <mh@glandium.org>
To: Sven <svoop@delirium.ch>
Cc: git@vger.kernel.org
Subject: Re: [BUG REPORT] "git ls-remote http://git.domain.com/repo.git HEAD" doesn't work
Date: Sat, 14 Jun 2008 09:10:11 +0200	[thread overview]
Message-ID: <20080614071011.GA29699@glandium.org> (raw)
In-Reply-To: <loom.20080614T065448-251@post.gmane.org>

On Sat, Jun 14, 2008 at 07:03:36AM +0000, Sven wrote:
> Hi
> 
> Following up my recent post, I'm now pretty sure this is a bug. Apparently,
> ls-remote does not list the HEAD version when used over HTTP(S) whereas it does
> work otherwise. Check this out:
> 
> over HTTP - no HEAD listed here:
> git ls-remote http://www.kernel.org/pub/scm/git/git.git
> 
> over GIT - HEAD is listed in this case:
> git ls-remote git://github.com/lux/sitellite.git 
> 
> As Capistrano relies on "git ls-remote http://git.domain.com/repo.git HEAD" to
> find out which version to pull, you can't deploy from Git over HTTP(S) repos for
> now. Capistrano is the de facto standard for deploying Ruby on Rails (and
> related) web applications.
> 
> Thanks a lot for looking into this!! (My knowledge unfortunately doesn't allow
> me to submit a patch myself.)

$ GIT_CURL_VERBOSE=1 git ls-remote http://www.kernel.org/pub/scm/git/git.git HEAD
* Couldn't find host www.kernel.org in the .netrc file, using defaults
* About to connect() to www.kernel.org port 80 (#0)
*   Trying 204.152.191.37... * Connected to www.kernel.org (204.152.191.37) port 80 (#0)
> GET /pub/scm/git/git.git/info/refs HTTP/1.1
User-Agent: git/1.5.5.4
Host: www.kernel.org
Accept: */*

< HTTP/1.1 200 OK
< Date: Sat, 14 Jun 2008 07:08:36 GMT
< Server: Apache/2.2.2 (Fedora)
< Last-Modified: Sat, 14 Jun 2008 05:04:30 GMT
< ETag: "14225449-66de-44f9954509380"
< Accept-Ranges: bytes
< Content-Length: 26334
< Content-Type: text/plain; charset=UTF-8
< 
* Expire cleared
* Connection #0 to host www.kernel.org left intact

http://www.kernel.org/pub/scm/git/git.git/info/refs doesn't contain HEAD.
Shouldn't it ?

Mike

  reply	other threads:[~2008-06-14  7:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-14  7:03 [BUG REPORT] "git ls-remote http://git.domain.com/repo.git HEAD" doesn't work Sven
2008-06-14  7:10 ` Mike Hommey [this message]
2008-06-14  7:24   ` Junio C Hamano
2008-06-14  7:49     ` Sven
2008-06-14  9:02       ` Mike Hommey
2008-06-14  9:19         ` Jeff King
2008-06-14  9:28           ` Mike Hommey
2008-06-14  9:24         ` Sven
2008-06-14  9:31           ` [BUG REPORT] "git ls-remote http://git.domain.com/repo.git?HEAD" " Jeff King
2008-06-14  9:40             ` Sven
2008-06-14 18:09     ` [BUG REPORT] "git ls-remote http://git.domain.com/repo.git HEAD" " Junio C Hamano
2008-06-14 18:26       ` [BUG REPORT] Sven
2008-06-14 23:37         ` Jeff King

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080614071011.GA29699@glandium.org \
    --to=mh@glandium.org \
    --cc=git@vger.kernel.org \
    --cc=svoop@delirium.ch \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).