From: "Torsten Bögershausen" <tboegi@web.de>
To: Reuben Hawkins <reubenhwk@gmail.com>, git@vger.kernel.org
Cc: dpotapov@gmail.com
Subject: Re: [PATCH 1/2] init-db.c: honor case on case preserving fs
Date: Sat, 01 Feb 2014 13:17:47 +0100 [thread overview]
Message-ID: <52ECE5EB.6090304@web.de> (raw)
In-Reply-To: <1391246067-30499-1-git-send-email-reubenhwk@gmail.com>
On 2014-02-01 10.14, Reuben Hawkins wrote:
> Most case-insensitive filesystems are case-preserving. In these
> filesystems (such as HFS+ on OS X) you can name a file Filename.txt,
> then rename the file to FileName.txt. That file will be accessible
> by both filenames, but the case is otherwise honored. We don't want
> to have git ignore case on these case-preserving filesystem
> implementations.
Yes, we want.
Because the file system will treat "Filename.txt" and "FileName.txt"
the same.
Whatever is on disc, the OS will not distinguish them.
(On a case-insensitive HFS+ partition).
And when core.ignorecase == true, Git does the same what the OS does,
ignore the case.
Could you describe the problems more in detail ?
Could you supply a test case, (or a short script) which shows
the problem and makes it reproducable for others?
Which problems does your patch solve, which can not be solved
by setting core.ignorecase==false manually?
/Torsten
next prev parent reply other threads:[~2014-02-01 12:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-01 9:14 [PATCH 1/2] init-db.c: honor case on case preserving fs Reuben Hawkins
2014-02-01 9:14 ` [PATCH 2/2] init-db.c: factor out probe_case_sensitivity func Reuben Hawkins
2014-02-01 12:17 ` Torsten Bögershausen [this message]
[not found] ` <CAD_8n+RWNZkGO31XveDuSy2aXv5uAMy087AUUu2+wXtO=MngAg@mail.gmail.com>
2014-02-01 23:47 ` [PATCH 1/2] init-db.c: honor case on case preserving fs Dmitry Potapov
2014-02-02 18:08 ` Junio C Hamano
[not found] ` <CAHkcotg3McjrnQ_rLi4YpLAauMQT6U0kjEp1eu+6jxbuRY5zrA@mail.gmail.com>
[not found] ` <CAD_8n+TQ4i2Z5zePXCTqpdF8mpRrzzKjDUB-NxZ1PJAwek-y1w@mail.gmail.com>
2014-02-02 5:46 ` Dmitry Potapov
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=52ECE5EB.6090304@web.de \
--to=tboegi@web.de \
--cc=dpotapov@gmail.com \
--cc=git@vger.kernel.org \
--cc=reubenhwk@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.