On Tue, Oct 30, 2007 at 07:59:45AM -0700, Linus Torvalds wrote:Well, only the last one actually looks like a URL, so that is the only this discussion is about. I don't think anyone is suggesting that the first three be changed at all. So, to use your terminology, git has a variety of ways to specify a repo name, one of which happens to be a URL (or looks like one). The suggestion is that we should make that way (and only that way) behave like a RFC URL. And git should be consistent with web browsers, automatically quoting things it gets passed. I think the only point of contention is probably how to deal with URLs that git receives that are already quoted. 1. We ignore the quoting and re-encode everything for the http transport. 2. We honour the encoding and decode everything for the git transport. 3. We handle git:// and http:// different, so that the three git:// URLs below refer to different repositories, while the three http:// URLs give refer to the same repository. The third possibility is probably what we do now, which is why I am suggesting git is inconsistent. The first will fall down when using a repository that is colocated, and somebody copies a URL from the web browsers location bar (which will be properly encoded). Which leaves the second. Tom - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Mark Lord | 2.6.25-rc8: FTP transfer errors |
| Kamalesh Babulal | Re: 2.6.23-rc6-mm1 |
| Greg Kroah-Hartman | [PATCH 025/196] paride: Convert from class_device to device for block/paride |
| Stephen Rothwell | Announce: Linux-next (Or Andrew's dream :-)) |
git: | |
| Linus Torvalds | Re: iptables very slow after commit 784544739a25c30637397ace5489eeb6e15d7d49 |
| David Miller | Re: [GIT]: Networking |
| Gerrit Renker | [PATCH 18/37] dccp: Support for Mandatory options |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
