From: Linus Torvalds <torvalds@linux-foundation.org>
To: David Kastrup <dak@gnu.org>
Cc: Jakub Narebski <jnareb@gmail.com>, git@vger.kernel.org
Subject: Re: remote#branch
Date: Wed, 31 Oct 2007 08:28:36 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.999.0710310816180.30120@woody.linux-foundation.org> (raw)
In-Reply-To: <85lk9jzsxb.fsf@lola.goethe.zz>
On Wed, 31 Oct 2007, David Kastrup wrote:
>
> I can click on links in my mail reader, and the above is not recognized
> as one. <URL:http://host/git repo with spaces in the path> would likely
> work.
I don't think this whole discussion is relevant at all.
Why?
Because we don't care! This is *exactly* why I brought up the whole
discussion about "interoperability with a web browser", and pointed out
that there is no such thing *anyway*, since a GIT URL is generally not
suitable for browsing _regardless_ of any encoding issues!
So it doesn't matter one whit if a mail client recognizes GIT URL's or
not! Because the mail client cannot do the right thing with them anyway,
and would generally think that it's something that it should highlight so
that you can browse it!
Besides, you generally shouldn't use http for git URL's in the first
place, and they are very much a secondary citizen. Yes, some people use
them because they have firewall issues, and they *work*, but giving them
as examples of GIT URL's and discussing them as it they were a big deal is
just *stupid* when no other - more realistic - git url works that way
anyway.
This was the whole and only point of my "interoperability" thing. The GIT
URL's - even when they are perfectly well-formed URL's (which is basically
100% of the time, since no current git server tends to put things like
spaces in the path anyway) - are simply in a different "space" than most
other URL's.
You cannot feed them to a web browser or a file browser anyway, since the
URL is actually mal-formed (on purpose) in *another* and more fundamental
way: it doesn't say what the "application domain" is, since it basically
just assumes that the application domain is git, and the "scheme" part of
the URL really talks only about the _protocol_, not about the fact that
it's a git thing.
So if you wanted to be inter-operable, you'd have add the "git" part to
the scheme, and do the (insane, in my opinion) cogito thing with
"git+http://xyz.hjashja/" thing!
See? Otherwise no non-git program could understand *anyway* that it's a
git address, and not meant to be some html thing.
So to summarise:
- the only way to make git interoperate would be to be user-UNfriendly
with stupid markers that no git program really needs or wants, and by
making the escaping depend on the form of the GIT URL.
But hey, if people want to screw up git even more, and make the "git+"
crap also encode the address, I don't care. I would never *ever* use the
"git+xyz://" forms anyway. They're stupid and useless, but if you want to
have programs automatically do something magical about git url's, you'd
need that "git+" thing.
Personally, I think it's a much better idea to just be git-specific.
Because realistically, nobody is ever going to really be anything else
anyway. There is nothing you can sanely do with a git link, unless it's
something very git specific and conscious in the first place!
Linus
next prev parent reply other threads:[~2007-10-31 15:32 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 21:38 [PATCH] Git homepage: remove all the references to Cogito Paolo Ciarrocchi
2007-10-16 2:19 ` Petr Baudis
2007-10-16 7:50 ` Matthieu Moy
2007-10-16 8:01 ` Paolo Ciarrocchi
2007-10-16 9:04 ` [PATCH] gitweb: Speed up get_projects_list for large source trees Luke Lu
2007-10-16 16:55 ` Andreas Ericsson
2007-10-16 23:20 ` Petr Baudis
2007-10-16 10:49 ` cogito and remote#branch, was Re: [PATCH] Git homepage: remove all the references to Cogito Johannes Schindelin
2007-10-16 21:09 ` remote#branch Jan Hudec
2007-10-16 21:35 ` remote#branch Johannes Schindelin
2007-10-27 20:47 ` remote#branch Jan Hudec
2007-10-27 23:01 ` remote#branch Johannes Schindelin
2007-10-29 17:40 ` remote#branch Jan Hudec
2007-10-29 18:17 ` remote#branch Linus Torvalds
2007-10-29 21:49 ` remote#branch Theodore Tso
2007-10-29 22:57 ` remote#branch Linus Torvalds
2007-10-29 23:49 ` remote#branch Johannes Schindelin
2007-10-30 3:01 ` remote#branch Theodore Tso
2007-10-30 3:40 ` remote#branch Junio C Hamano
2007-10-30 4:40 ` remote#branch Theodore Tso
2007-10-30 4:51 ` remote#branch Linus Torvalds
2007-10-30 5:37 ` remote#branch Tom Prince
2007-10-30 14:59 ` remote#branch Linus Torvalds
2007-10-30 16:02 ` remote#branch Tom Prince
2007-10-30 17:39 ` remote#branch Linus Torvalds
2007-10-30 17:49 ` remote#branch Matthieu Moy
2007-10-30 17:58 ` remote#branch Linus Torvalds
2007-10-30 18:19 ` remote#branch Linus Torvalds
2007-10-30 19:18 ` remote#branch Pascal Obry
2007-10-30 19:38 ` remote#branch Linus Torvalds
2007-10-30 20:15 ` remote#branch Randal L. Schwartz
2007-10-30 20:30 ` remote#branch Linus Torvalds
2007-10-30 20:36 ` remote#branch Nicolas Pitre
2007-10-30 23:58 ` remote#branch Jeff King
2007-10-31 0:12 ` remote#branch Jakub Narebski
2007-10-31 1:38 ` remote#branch Jeff King
2007-10-31 1:49 ` remote#branch Jakub Narebski
2007-10-31 1:57 ` remote#branch Jeff King
2007-10-31 7:09 ` remote#branch Andreas Ericsson
2007-10-31 8:35 ` remote#branch Mike Hommey
2007-10-31 9:03 ` remote#branch Andreas Ericsson
2007-10-31 9:15 ` remote#branch Mike Hommey
2007-11-01 0:22 ` remote#branch Jakub Narebski
2007-11-01 5:11 ` remote#branch Theodore Tso
2007-11-01 7:29 ` remote#branch Andreas Ericsson
2007-10-31 9:33 ` remote#branch Pascal Obry
2007-10-31 6:42 ` remote#branch David Kastrup
2007-10-31 15:28 ` Linus Torvalds [this message]
2007-10-31 20:47 ` remote#branch Jeff King
2007-10-31 21:01 ` remote#branch Linus Torvalds
2007-10-31 21:26 ` remote#branch Jeff King
2007-10-31 21:28 ` remote#branch Linus Torvalds
2007-10-31 21:07 ` remote#branch Andreas Ericsson
2007-10-31 21:31 ` remote#branch Jeff King
2007-10-31 6:39 ` remote#branch David Kastrup
2007-10-31 8:16 ` remote#branch Wincent Colaiuta
2007-10-31 8:25 ` remote#branch Robin Rosenberg
2007-10-31 9:34 ` remote#branch Pascal Obry
2007-10-31 17:13 ` remote#branch Petr Baudis
2007-10-30 19:15 ` remote#branch Pascal Obry
2007-10-30 19:36 ` remote#branch Jan Hudec
2007-10-30 19:53 ` remote#branch Linus Torvalds
2007-10-31 19:29 ` remote#branch Erik Warendorph
2007-10-30 10:02 ` remote#branch Johannes Schindelin
2007-10-31 0:41 ` remote#branch Martin Langhoff
2007-10-31 0:59 ` remote#branch Linus Torvalds
2007-10-31 1:43 ` remote#branch Jeff King
2007-10-31 1:49 ` remote#branch Martin Langhoff
2007-10-31 1:59 ` remote#branch Jeff King
2007-10-31 3:08 ` remote#branch Johannes Schindelin
2007-10-30 4:50 ` remote#branch Linus Torvalds
2007-10-29 18:32 ` remote#branch Johannes Schindelin
2007-10-16 22:16 ` cogito and remote#branch, was Re: [PATCH] Git homepage: remove all the references to Cogito Jonas Fonseca
2007-10-31 17:09 ` Petr Baudis
2007-10-31 21:17 ` Jonas Fonseca
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=alpine.LFD.0.999.0710310816180.30120@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=dak@gnu.org \
--cc=git@vger.kernel.org \
--cc=jnareb@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.
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).