On Tue, Oct 30, 2007 at 07:59:45 -0700, Linus Torvalds wrote:
quoted text
> > So, how should git deal with
> >=20
> > git://repo.or.cz/linux-2.6/linux acpi-2.6/ibm-acpi-2.6.git
> > git://repo.or.cz/linux-2.6/linux+acpi-2.6/ibm-acpi-2.6.git
> > git://repo.or.cz/linux-2.6/linux%20acpi-2.6/ibm-acpi-2.6.git
>=20
> The way it has always cared. Git itself does no quoting what-so-ever=20
> (except for the *argument* quoting etc that it needs).
>=20
> Now, the *transport* back-end may end up quoting it, of course, the same=
=20
quoted text
> way it may end up using some random protocol. The user shouldn't care=20
> about the implementation details!
>=20
> In the case of the git transport, there is no quoting even by the=20
> transport protocol. In the case of http, libcurl would hopefully quote fo=
r=20
quoted text
> us.

So the three addresses will all be different, right?

quoted text
> > compared to=20
> >=20
> > http://repo.or.cz/linux-2.6/linux acpi-2.6/ibm-acpi-2.6.git
> > http://repo.or.cz/linux-2.6/linux+acpi-2.6/ibm-acpi-2.6.git
> > http://repo.or.cz/linux-2.6/linux%20acpi-2.6/ibm-acpi-2.6.git
>=20
> No difference, what-so-ever, that I can see. Git doesn't quote it.

Yes. But the server will unquote it. ' ' should not have been there, but it=
's
just passed through if it was. '+' is quoting for ' ' and '%20' is quoting
for ' ' as well. Therefore all these three addresses are the *SAME*.

Now the user expectation will be that when these are the same, the git://
ones above will be as well. But they are not. This is not about following a=
ny
RFC for sake of it, but about being consistent with ourselves.

quoted text
> Notice how the fact that we use http:// doesn't actually mean that you ca=
n=20
quoted text
> feed the result to a web browser anyway? It's not like you get a "link"=
=20
quoted text
> that git follows. You get a name.
>=20
> Yes, you can try to "co-locate" things so that something smart=20
> disambiguates (maybe have an "index.html" file, so a web browser gets a=
=20
quoted text
> gitweb page, and git gets the raw data). But even then, notice how even=
=20
quoted text
> web browser will do the quoting for you: try
>=20
> 	firefox "http://www.google.com/search?q=3DHtml spaces"
>=20
> just for fun.

Sure. There is no abiguity in decoding this, so why refuse it.

quoted text
> [...]
>  - <remote shorthand> ("origin")
>  - <path> ("../git.git")
>  - <host>:<path> ("master.kernel.org:/pub/scm/...")
>  - <protocol>://<host>/<path> ("git://repo.or.cz/...")
>=20
> See? We may not follow RFC's, but we follow "easy to use".

The first three don't look like URL ("URL" always means the thing defined by
RFC 2396, at least to me), so I don't expect any quoting there. But for the
last case http:// (and for that matter, sftp://) do use quoting, so I would
expect the quoting of something that differs only by starting with git:// to
work the same.=20

--=20
						 Jan 'Bulb' Hudec <bulb@ucw.cz>