From: gmane2010@cfaerber.name (Claus Färber)
To: git@vger.kernel.org
Subject: Re: Git under Windows should warn or fail on entities differning only in case
Date: 12 Feb 2010 19:19:00 +0100 [thread overview]
Message-ID: <BIjfD8Ogt6D@mid.cfaerber.name> (raw)
In-Reply-To: 1265978433.7519.6.camel@chumley
David Hagood <david.hagood@gmail.com> schrieb/wrote:
> If you have 2 entities in a directory which have names differing only
> in case, e.g. "foo" and "FOO", under a REAL operating system with case
> sensitive file system semantics, this is no problem. However, under
> Windows and their wonderful "Case preserving but case insensitive"
> semantics, "FOO" and "foo" would be the same file,...
Mac OS X has the same problem.
Further, it does not preserve the Unicode normalisation form.
Claus
next prev parent reply other threads:[~2010-02-12 20:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-12 12:40 Git under Windows should warn or fail on entities differning only in case David Hagood
2010-02-12 13:14 ` Johannes Schindelin
2010-02-12 17:31 ` Pete Harlan
2010-02-12 21:02 ` david.hagood
2010-02-12 18:19 ` Claus Färber [this message]
2010-02-12 20:38 ` Julian Phillips
2010-02-13 6:05 ` Daniel Barkalow
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BIjfD8Ogt6D@mid.cfaerber.name \
--to=gmane2010@cfaerber.name \
--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.
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 NNTP newsgroup(s).