El 31/10/2007, a las 7:39, David Kastrup escribió:
Jeff King <peff@xxxxxxxx> writes:
I didn't ask for RFC quoting, but a nice side effect of URL syntax is
that they are machine parseable. If you wanted to write a tool to
pick
the URLs out of this email and clone them as git repos, then how do
you
find the end of:
http://host/git repo with spaces in the path
compared to:
http://host/git+repo+with+spaces+in+the+path
You just write <URL:http://host/git repo with spaces in the path> and
have a good chance it will work.
As a data point, my email client correctly highlights only this one as
a URL:
http://host/git+repo+with+spaces+in+the+path
Both of these are incorrectly highlighted:
http://host/git repo with spaces in the path
<URL:http://host/git repo with spaces in the path>
And this one too:
<http://host/git repo with spaces in the path>
So what does this mean in practice? I can right-click on the first one
and choose "Copy". All the other ones I have to left-click and drag,
being careful to limit the selection to the appropriate left and right
boundaries.
Whether or not this is a big enough deal to actually care about is
open to debate (obviously). Personally, I don't care too much seeing
as I never use paths with spaces in them for this kind of thing.
Cheers,
Wincent
-
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
