Re: remote#branch

[Linus Torvalds <torvalds@linux-foundation.org>]

On Wed, 31 Oct 2007, Jeff King wrote:
> 
> Yes, this means that if you have a bizarre repo name, you can't
> necessarily switch between host:file syntax and git:// syntax by simple
> cut and paste. But you really can't _anyway_, since there is no
> guarantee that they are rooted at the same location, or have the same
> view of the filesystem.

.. but in practice it works fine, especially for something like kernel.org 
where it really *is* the same filesystem, just mirrored out.

Also, more importantly, I think the quoting is *stupid*. It adds pointless 
code for absolutely zero gain. Are you going to unquote '/'? Or how about 
'~'?

It's much nicer to just not have the quoting issue at all. Repo names are 
names. Straight up.

> > Personally, I think it's a much better idea to just be git-specific. 
> 
> Then why in the world did you choose a specifier syntax that looks
> _exactly_ like a URL?

.. because it's a simple format, and it *works*. The same way INI config 
files are simple and *work*.

And because I didn't think I'd have to care about people who like f*cking 
around with idiotic details, rather than just get something that is useful 
and works!

If you don't like the fact that git doesn't quote, just don't use the 
magic characters. It's that easy. And if somebody quotes the '/', just 
tell him off for being an ass.

But git can and should do the *sane* thing.

			Linus