From: Jeff King <peff@peff.net>
To: kinchit raja <kinchit15@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Bug: Git checkout case Insensitive branch name compare
Date: Tue, 11 Jul 2017 03:38:36 -0400 [thread overview]
Message-ID: <20170711073836.3nclljuzqgwdg6t5@sigill.intra.peff.net> (raw)
In-Reply-To: <CAKvSMhhO7RwiZfpcLR3cK2TXF-v9MrO1N33t8BqX=8f9z=Gd0w@mail.gmail.com>
On Mon, Jul 10, 2017 at 01:15:40PM -0700, kinchit raja wrote:
> Bugs Details:
>
> Git checkout case Insensitive branch name compare
Right, this is known. Branch names (and all ref names) are case
sensitive in Git. Storage on a case-insensitive filesystem may lead to
confusion if you mix the cases. Sometimes it will work, and sometimes it
will create quite confusing results. One suggested path forward is to
encode characters in the filesystem. See:
http://public-inbox.org/git/20170705083611.jgxbp4sqogicfwdb@sigill.intra.peff.net/
and further down-thread:
http://public-inbox.org/git/xmqqo9sxdwjp.fsf@gitster.mtv.corp.google.com/
for some recent discussion.
-Peff
prev parent reply other threads:[~2017-07-11 7:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 20:15 Bug: Git checkout case Insensitive branch name compare kinchit raja
2017-07-11 7:38 ` Jeff King [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=20170711073836.3nclljuzqgwdg6t5@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=kinchit15@gmail.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).