From: Lars Schneider <larsxschneider@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Dakota Hawkins <dakota@dakotahawkins.com>,
Duy Nguyen <pclouds@gmail.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Stefan Beller <sbeller@google.com>, git <git@vger.kernel.org>
Subject: Re: [RFC] Case insensitive Git attributes
Date: Mon, 23 Jan 2017 19:42:40 +0100 [thread overview]
Message-ID: <C265204B-BCCF-4085-9933-F28EB459CFB9@gmail.com> (raw)
In-Reply-To: <xmqqvat5sjym.fsf@gitster.mtv.corp.google.com>
> On 23 Jan 2017, at 19:35, Junio C Hamano <gitster@pobox.com> wrote:
>
> Dakota Hawkins <dakota@dakotahawkins.com> writes:
>
>> Apologies for the delayed bump. I think because we're talking about
>> affecting the behavior of .gitattributes that it would be better to
>> have a distinct .gitattributes option, whether or not you also have a
>> similar config option.
>
> As I know I am on the To: line of the message I am responding to,
> let me quicly let you know that I won't be responding to this thread
> for a while as I don't recall what the discussion was about. I will
> after I'll dig and find out what the thread was about but it won't
> happen immediately. Sorry about that.
Problem:
Git attributes for path names are generally case sensitive. However, on
a case insensitive file system (e.g. macOS/Windows) they appear to be
case insensitive (`*.bar` would match `foo.bar` and `foo.BAR`). That
works great until a Git users joins the party with a case sensitive file
system. For this Git user the attributes pattern only matches files with
the exact case (*.bar` would match only `foo.bar`).
Question/Proposal:
Could we introduce some flag to signal that certain attribute patterns
are always case insensitive?
Thread:
http://public-inbox.org/git/C83BE22D-EAC8-49E2-AEE3-22D4A99AE205@gmail.com/#t
Cheers,
Lars
next prev parent reply other threads:[~2017-01-23 18:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-22 19:25 [RFC] Case insensitive Git attributes Dakota Hawkins
2017-01-23 18:35 ` Junio C Hamano
2017-01-23 18:42 ` Lars Schneider [this message]
2017-01-23 19:25 ` Junio C Hamano
2017-01-23 19:38 ` Junio C Hamano
2017-01-24 9:49 ` Lars Schneider
-- strict thread matches above, loose matches on Subject: below --
2016-10-17 1:04 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
2016-10-17 8:55 ` Johannes Schindelin
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=C265204B-BCCF-4085-9933-F28EB459CFB9@gmail.com \
--to=larsxschneider@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=dakota@dakotahawkins.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.com \
--cc=sbeller@google.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.
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).