From: Lars Schneider <larsxschneider@gmail.com>
To: git <git@vger.kernel.org>
Subject: [RFC] Case insensitive Git attributes
Date: Sun, 16 Oct 2016 18:04:26 -0700 [thread overview]
Message-ID: <C83BE22D-EAC8-49E2-AEE3-22D4A99AE205@gmail.com> (raw)
Hi,
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 only files that match the exact case of the
attribute pattern get the attributes (only `foo.bar`).
This inconsistent behavior can confuse Git users. An advanced Git user
could use a glob pattern (e.g. `*.[bB][aA][rR]) to match files in a
case insensitive way. However, this can get confusing quickly, too.
I wonder if we can do something about this. One idea could be to add an
attribute "case-sensitive" (or "caseSensitive") and set it to false
(if desired) for all files in .gitattributes for a given repo.
### .gitattributes example ###
* case-sensitive=false
*.bar something
###
I haven't looked into the feasibility of an implementation, yet. However,
would that be an acceptable approach?
Thanks,
Lars
next reply other threads:[~2016-10-17 1:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 1:04 Lars Schneider [this message]
2016-10-17 3:07 ` [RFC] Case insensitive Git attributes 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
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=C83BE22D-EAC8-49E2-AEE3-22D4A99AE205@gmail.com \
--to=larsxschneider@gmail.com \
--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).