From: Konstantin Khomoutov <flatworm@users.sourceforge.net>
To: Konstantin Khomoutov <flatworm@users.sourceforge.net>
Cc: Kirill Likhodedov <Kirill.Likhodedov@jetbrains.com>, git@vger.kernel.org
Subject: Re: Set core.ignorecase globally
Date: Fri, 2 Nov 2012 19:15:16 +0400 [thread overview]
Message-ID: <20121102191516.e8b7d448ff76b45990e14b1d@domain007.com> (raw)
In-Reply-To: <20121102190337.66a08366de41d29e745b0e4c@domain007.com>
On Fri, 2 Nov 2012 19:03:37 +0400
Konstantin Khomoutov <flatworm@users.sourceforge.net> wrote:
> > Currently, core.ignorecase is set to true on case insensitive system
> > like Windows or Mac on `git init` and `git clone`, and this setting
> > is local to the created/cloned repository.
> [...]
> > I suggest to set this globally by default when Git is installed,
> > because there is little sense to have this option false on case
> > insensitive systems (it will lead to confusions when renaming a file
> > by changing only the case of letters).
>
> Case sensitivity is a property of a file system, not the OS.
> What if I mount a device with ext3 file system via ext2fsd driver in
> on my Windows workstation? extN have POSIX semantics so it's
> pointless to enforce case insensitivity on them. The same possibly
> applies to NFS mounts.
>
> Also note that NTFS (at least by default) is case insensitive but is
> case preserving, observe:
[...]
On the other hand, on NTFS, if I unset core.ignorecase or set it to
false locally, `git mv foo Foo` fails to rename a tracked file "foo"
with the "destination file exists" error. I would say I would expect it
to work under the conditions I've just described. Not sure if this
thould be considered a bug in Git for Windows or not -- would be great
to hear opinions of the msysgit port developers.
next prev parent reply other threads:[~2012-11-02 15:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 14:39 Set core.ignorecase globally Kirill Likhodedov
2012-11-02 15:03 ` Konstantin Khomoutov
2012-11-02 15:15 ` Konstantin Khomoutov [this message]
2012-11-02 20:05 ` Torsten Bögershausen
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=20121102191516.e8b7d448ff76b45990e14b1d@domain007.com \
--to=flatworm@users.sourceforge.net \
--cc=Kirill.Likhodedov@jetbrains.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).