Mike Hommey wrote:
On Wed, Oct 31, 2007 at 08:09:01AM +0100, Andreas Ericsson <ae@xxxxxx> wrote:
Jeff King wrote:
On Wed, Oct 31, 2007 at 02:49:16AM +0100, Jakub Narebski wrote:
...which is a quoting mechanism, and it's not even one commonly used in
emails (i.e., people have written "parse a URL from this text" scripts
for RFC-encoded URLs, but _not_ for shell quoting).
I don't think RFC-encoding is quoting mechanism used in emails, either.
That's funny, because I have hundreds of mails where that is the case,
and none where people used shell-quoting. Most URLs don't _need_ any
encoding, so we don't notice either way. But are you honestly telling me
that if you needed to communicate a URL with a space via email, you
would write:
'http://foo.tld/url with a space'
rather than:
http://foo.tld/url+with+a+space
?
I think 99% of all URL's communicated via email are copy-pasted from a
webbrowsers location bar. I believe most git urls (or grls, or whatever
you wanna call them) communicated via email are copy-pasted from ones
config, or written out manually.
Or copied from gitweb.
Perhaps, but I've never seen that done. Partly because you can't be sure
the HTTP url is the same as the git address (perhaps people are used to
this from CVS and the likes), and partly because you'd, for most cases,
want to use git:// or ssh transport instead of http.
It might be nifty to have gitweb print some git-valid locator for a repo
though, or even a full copy-pastable "git clone git://host/path/to/repo.git"
command-line thingie. I'll look into it when I have leisure.
--
Andreas Ericsson andreas.ericsson@xxxxxx
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
