On Tue, 30 Oct 2007, Linus Torvalds wrote: > > So if you want to make that RFC have any relevance what-so-ever, then show > some interoperability issue. Which is why I'm bringing up a web browser: > that interop issue simply *does*not*exist*. Btw, the reason I care is that the whole ".. but it's a standard" thinking really is dangerous. It's how you create absolute and utter crap. It's why I have also brought up XML in this discussion, because XML is a classic example of something where this ".. but it's a standard" thinking has resulted in really bad solutions. It's pushed as a way to "interoperate", but then, since everybody does different things, the only thing you can actually interoperate with is by having a common parsing library for a REALLY HORRIBLY BAD FORMAT! The same is true of a URL. What is there to interoperate with? The whole (and only) point of the git remote URL is to point git to a different git repository. There's no other reason to use it. So the only possible case we care about interoperability is with other git uses. And those other git uses are not RFC1738-quoted, are they? Linus - 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