Thread (14 messages) 14 messages, 5 authors, 2016-12-12

Re: [BUG] Colon in remote urls

From: Philip Oakley <hidden>
Date: 2016-12-11 14:51:43

From: "Klaus Ethgen" <redacted>
To: <redacted>
Am Sa den 10. Dez 2016 um 19:18 schrieb Johannes Schindelin:
quoted
On Sat, 10 Dec 2016, Klaus Ethgen wrote:
quoted
Am Fr den  9. Dez 2016 um 22:32 schrieb Johannes Sixt:
quoted
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help