Mike Hommey <mh@xxxxxxxxxxxx> writes: > In fact, the parser doesn't even reject the one that is considered > invalid (the first). My question was what the desired behaviour is, and if your "fix" gives us that desired outcome. > (Also, the discussion back then was about > git://[example.com:123]:/path/to/repo, not > git://[example.com:123]/path/to/repo) I thought these two ought to be equivalent: <scheme>://<host>:/<localpart> <scheme>://<host>/<localpart> so the distinction shouldn't matter, no? The former's last colon is "I wanted to write a custom port, but didn't spell it out, which is equivalent to spelling out the default port, which in turn is equivalent to not having that :<port> at all. -- 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