From: "Matt Seitz (matseitz)" <matseitz@cisco.com>
To: <git@vger.kernel.org>
Subject: Re: [PATCH 2/2] git-sh-setup: work around Cygwin path handling gotchas
Date: Mon, 21 May 2012 16:51:04 -0700 [thread overview]
Message-ID: <70952A932255A2489522275A628B97C31348C4AB@xmb-sjc-233.amer.cisco.com> (raw)
"Junio C Hamano" <gitster@pobox.com> wrote in message
news:<7vaa116ulx.fsf@alter.siamese.dyndns.org>...
>
> 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?
next reply other threads:[~2012-05-21 23:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 23:51 Matt Seitz (matseitz) [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-05-14 6:02 Git commit path vs rebase path Johannes Sixt
2012-05-16 18:00 ` [PATCH 0/2] " Junio C Hamano
2012-05-16 18:00 ` [PATCH 2/2] git-sh-setup: work around Cygwin path handling gotchas Junio C Hamano
2012-05-16 18:51 ` Steven Penny
2012-05-16 19:02 ` Junio C Hamano
2012-05-17 23:15 ` Ramsay Jones
2012-05-18 2:34 ` Junio C Hamano
2012-05-19 0:43 ` Steven Penny
2012-05-21 18:43 ` Ramsay Jones
2012-05-21 22:24 ` Junio C Hamano
2012-05-24 18:27 ` Ramsay Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=70952A932255A2489522275A628B97C31348C4AB@xmb-sjc-233.amer.cisco.com \
--to=matseitz@cisco.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).