From: Junio C Hamano <gitster@pobox•com>
To: Duy Nguyen <pclouds@gmail•com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx•de>,
Stefan Beller <sbeller@google•com>,
Lars Schneider <larsxschneider@gmail•com>,
git <git@vger•kernel.org>
Subject: Re: [RFC] Case insensitive Git attributes
Date: Mon, 17 Oct 2016 10:50:21 -0700 [thread overview]
Message-ID: <xmqqzim2vp9e.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CACsJy8ASnvryrrWvr4ACWL_9oeKgE_4SUqcRHGf+Y6kcaeDUhg@mail.gmail.com> (Duy Nguyen's message of "Mon, 17 Oct 2016 18:02:50 +0700")
Duy Nguyen <pclouds@gmail•com> writes:
> I agree. Which is why I wrote "we probably want something in the same
> spirit but limited to .gitattributes and .gitignore only". In other
> words we could have core.someName that makes .gitattributes and
> .gitignore patterns case-insensitive (or core-sensitive). If it's
> present, it overrides core.ignoreCase. If it's not present,
> core.ignoreCase decides. I'm just not sure if the new config should
> cover everything involving filename's case in git. That's too big to
> fit in my head.
Once I stopped thinking about this as "filename's case", it does fit
my head ;-)
I view the proposed knob as making patterns in .gitattributes and
.gitignore case insensitive, iow, it is a lazy and useful short-hand
for (mentally) editing "*.c attr" to "*.[cC] attr" without touching
these files.
And I agree that the knob that is missing in today's Git should
default to whatever core.ignoreCase's value is, iow, on case
insensitive filesystem, attr and ignore may match case insensitively
in today's Git, but when the knob is introduced, it should allow
forcing case sensitive match there by setting it to false, just like
the knob is proposed to be used in the oppositite direction to force
case insensitive match regardless of the case insensitiveness of the
underlying filesystem.
next prev parent reply other threads:[~2016-10-17 17:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 1:04 [RFC] Case insensitive Git attributes Lars Schneider
2016-10-17 3:07 ` Stefan Beller
2016-10-17 4:24 ` Torsten Bögershausen
2016-10-17 8:57 ` Johannes Schindelin
2016-10-17 9:12 ` Duy Nguyen
2016-10-17 10:46 ` Johannes Schindelin
2016-10-17 11:02 ` Duy Nguyen
2016-10-17 17:50 ` Junio C Hamano [this message]
2016-10-17 8:55 ` Johannes Schindelin
-- strict thread matches above, loose matches on Subject: below --
2017-01-22 19:25 Dakota Hawkins
2017-01-23 18:35 ` Junio C Hamano
2017-01-23 18:42 ` Lars Schneider
2017-01-23 19:25 ` Junio C Hamano
2017-01-23 19:38 ` Junio C Hamano
2017-01-24 9:49 ` Lars Schneider
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=xmqqzim2vp9e.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=Johannes.Schindelin@gmx$(echo .)de \
--cc=git@vger$(echo .)kernel.org \
--cc=larsxschneider@gmail$(echo .)com \
--cc=pclouds@gmail$(echo .)com \
--cc=sbeller@google$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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