git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Scott Chacon <schacon@gmail.com>, git@vger.kernel.org
Subject: Re: git://github.com/some/thing.git/?
Date: Tue, 27 Mar 2012 12:33:39 -0400	[thread overview]
Message-ID: <20120327163339.GA5941@sigill.intra.peff.net> (raw)
In-Reply-To: <7vpqbyjbbx.fsf@alter.siamese.dyndns.org>

On Tue, Mar 27, 2012 at 08:46:42AM -0700, Junio C Hamano wrote:

> I just noticed that
> 
> 	git ls-remote git://repo.or.cz/alt-git.git/
> 
> works, but neither of the following does:
> 
> 	git ls-remote git://git://github.com/gitster/git.git/
> 	git ls-remote git://git://github.com/gitster/git/
> 
> It is just a minor irritation but it would be really nice if you can fix
> it (please don't spend too much time on it if it is too involved, though).

Of course they don't work, they are malformed. :)

It took me a minute to figure it out, but I assume the interesting part
is the trailing slash?

Interestingly, this does work for http URLs, because we do some
normalization on the client side (and then append things like
"info/refs"). I wonder if we should do similar normalization for other
protocols.

Even with that, though, I think it would be good for the server to be
liberal in what it accepts.

-Peff

  reply	other threads:[~2012-03-27 16:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-27 15:46 git://github.com/some/thing.git/? Junio C Hamano
2012-03-27 16:33 ` Jeff King [this message]
2012-03-27 18:25   ` git://github.com/some/thing.git/? Junio C Hamano
2012-03-27 18:38     ` git://github.com/some/thing.git/? Jeff King
2012-03-27 18:47       ` git://github.com/some/thing.git/? Jonathan Nieder
2012-03-28  4:28         ` git://github.com/some/thing.git/? Jeff King
2012-03-27 18:54       ` git://github.com/some/thing.git/? Junio C Hamano
2012-03-27 17:54 ` git://github.com/some/thing.git/? Kevin

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=20120327163339.GA5941@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=schacon@gmail.com \
    /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).