Re: [PATCH v2 0/6] Extensions of core.ignorecase=true support

Hello Johannes,

Here is the use case I was thinking of.

Let's say I want to have .gitignore be case insensitive with respect
to matches so I can simplify the file by not having [D][d]ebug sorts
of messes. But let's say I also want to support files whose names only
differ by case (just like Unix supports). Can your current patch
series support this? Does the current patch series break this?

Could you share how this would or would not work, and if not, how you
might accomplish this?

Thanks,

Bob

On Sun, Oct 3, 2010 at 2:12 PM, Johannes Sixt [off-list ref] wrote:

On Sonntag, 3. Oktober 2010, Robert Buck wrote:

quoted

So I could we please separate the behaviors that change intent
(folding) from the behaviors that merely alter how things are
displayed (listing) by splitting this into two separate properties?
For example,

core.casepreserving=true|false
core.caseinsensitive=true|false

The former property would control folding, the latter property would
apply to listing and pattern matching. Then people could opt out of
the folding behaviors (add, import), while continuing to adopt listing
and pattern matching (status, ls, ignore).

core.ignorecase has a very well-defined meaning: It describes whether the
worktree lives on a filesystem that is case-insensitive. Perhaps you could
help me understand your case if you gave examples and a use-case? I have a
slight suspicion that your wish is orthogonal to core.ignorecase.

-- Hannes