From: Bryan Turner <bturner@atlassian.com>
To: Alex Brachet-Mialot <alexbrachetmialot@gmail.com>
Cc: Git Users <git@vger.kernel.org>
Subject: Re: [Bug] Unexpected behavior on case insensitive filesystems
Date: Tue, 2 Jul 2019 12:05:56 -0700 [thread overview]
Message-ID: <CAGyf7-Ewm3A7h0vcbahMM+Jf=TcygVrkUob5YaAdH9HByh3asw@mail.gmail.com> (raw)
In-Reply-To: <CAOt2X9sqbpK2qaKk9uf7fL=WCdzJr4+bx-0CsgjssTKkEhd++Q@mail.gmail.com>
On Tue, Jul 2, 2019 at 10:23 AM Alex Brachet-Mialot
<alexbrachetmialot@gmail.com> wrote:
>
> Branches behave weirdly for case insensitive filesystems, and I'm
> guessing other things as well. For example say I am on a branch other
> than master, checking out 'Master' will _work_, I will of course be on
> the right branch but git status will say I am on 'Master' (expected
> just 'master') and git branch will highlight no branch.
This comes up on the list fairly often. A couple of recent threads are:
https://public-inbox.org/git/d4d8d8208b6a41c380ecf20807763bcf@XCH15-05-02.nw.nos.boeing.com/t/#u
https://public-inbox.org/git/CAGyf7-E3-0SiqweoX-uLotwcCcy5MSxG6Zh+DRo6zQPKqTQQpA@mail.gmail.com/t/#u
This also comes up for files within a repository:
https://public-inbox.org/git/trinity-4a160867-2036-4f8a-8363-7bf2e021d840-1558184320864@3c-app-gmx-bs48/t/#u
https://public-inbox.org/git/AANLkTi=87fUaOH3Y0PVeeH5N7oCVVJyKY3jsf93jw-t7@mail.gmail.com/t/#u
The replies to the first thread explain the behavior, why it does what
it does, and why it hasn't been changed yet. It happens on
case-insensitive macOS filesystems and on NTFS on Windows.
Hope this helps!
Bryan
prev parent reply other threads:[~2019-07-02 19:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 17:22 [Bug] Unexpected behavior on case insensitive filesystems Alex Brachet-Mialot
2019-07-02 19:05 ` Bryan Turner [this message]
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='CAGyf7-Ewm3A7h0vcbahMM+Jf=TcygVrkUob5YaAdH9HByh3asw@mail.gmail.com' \
--to=bturner@atlassian.com \
--cc=alexbrachetmialot@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.
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).