git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Mike Hommey <mh@glandium.org>
To: Jeff King <peff@peff.net>
Cc: Sven <svoop@delirium.ch>, 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 11:28:18 +0200	[thread overview]
Message-ID: <20080614092818.GA2401@glandium.org> (raw)
In-Reply-To: <20080614091900.GA22538@sigill.intra.peff.net>

On Sat, Jun 14, 2008 at 05:19:00AM -0400, Jeff King wrote:
> On Sat, Jun 14, 2008 at 11:02:44AM +0200, Mike Hommey wrote:
> 
> > > How likely is it that ls-remote HEAD is added for HTTP as well rather than
> > > stripped for all protocols?
> > 
> > When someone sends a patch ;)
> 
> I'm not sure I can bring myself to wait for that. After all, it could
> take nearly negative seven weeks:
> 
>   $ git log -1 --pretty=tformat:'%s (%ar)' be885d96
>   Make ls-remote http://... list HEAD, like for git://... (7 weeks ago)

Erf, now I must blame myself to have taken a look at a very old
transport.c file ;)

Mike

  reply	other threads:[~2008-06-14  9:30 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
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 [this message]
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=20080614092818.GA2401@glandium.org \
    --to=mh@glandium.org \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --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).