Re: [BUG] Colon in remote urls
- From
Philip Oakley <philipoakley@iee.org>
- Date
- Dec 11, 2016, 14:51 UTC
- Message-ID
- <913EC5FA0C2B4452AF027A84786F08BB@PhilipOakley>
- In-Reply-To
- <20161211110208.642unp7c2i653sav@ikki.ethgen.ch>
From: "Klaus Ethgen" <Klaus@Ethgen.ch> To: <git@vger.kernel.org>
Show 19 quoted lines
> Am Sa den 10. Dez 2016 um 19:18 schrieb Johannes Schindelin: >> On Sat, 10 Dec 2016, Klaus Ethgen wrote: >> > Am Fr den 9. Dez 2016 um 22:32 schrieb Johannes Sixt: >> > > There are too many systems out there that use a backslash in path >> > > names. I >> > > don't think it is wise to use it also as the quoting character. >> > Well, the minority, I believe. And only the minority where the command >> > line git is used anywhere. >> >> Please provide evidence for such bold assumptions. > > How is it "bold" to see that the majority of widows users does not use > or even like command line tools. And as git is command line tool (most > of them), users does use third party tools instead of the original. > > I know companies where the "developers" doesn't even know of the > existent of a git command line use. They look with owe when they see > that I use a shell to use git. >
Hasn't this drifted a little off topic. The issue was typeable characters in URLs and how that affects the accessibility of various paths.
We (Git) should be avoiding lock-in to particular systems where possible.
--
Philip