Re: [PATCH 2/2] git-sh-setup: work around Cygwin path handling gotchas

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



"Junio C Hamano" <gitster@xxxxxxxxx> wrote in message
news:<7vaa116ulx.fsf@xxxxxxxxxxxxxxxxxxxxxxxx>...
> 
> If you _only_ allow editors that understands windows style paths, your
> patch may make sense, but doesn't it break editors that wants only
POSIX
> style paths?

The Cygwin Users' Guide says "Using native Win32 paths in Cygwin, while
possible, is generally inadvisable."

http://cygwin.com/cygwin-ug-net/using.html#pathnames-win32

Is this similar to the problem of line ending (POSIX lf vs. Windows
cr-lf)?  Windows Notepad won't correctly display files with lf line
endings, either.
So maybe this should be a configuration option, as with line endings?


--
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


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]