From: Duy Nguyen <pclouds@gmail.com>
To: Philip Oakley <philipoakley@iee.org>
Cc: Git List <git@vger.kernel.org>,
git-for-windows <git-for-windows@googlegroups.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [git-for-windows] Case insensitive branch names
Date: Mon, 21 Dec 2015 19:21:02 +0700 [thread overview]
Message-ID: <CACsJy8CEYaf9NA4J_2u1cqsikYvtR7nz=FEiwAxsKMLSREDhCg@mail.gmail.com> (raw)
In-Reply-To: <D350A5BC87B74A53B5BE4B10BC658208@PhilipOakley>
On Mon, Dec 21, 2015 at 6:01 PM, Philip Oakley <philipoakley@iee.org> wrote:
> On the Git User's list, Diego J. reported that:
>
> 'When I "checkout" a branch using different Upper Case/Lower Case than the
> original, the branch doesn't show in "git branch [--list]"' [1]
>
> While case sensitivity for filenames is a common issue on Windows and the
> like, I haven't seen any discussion regarding ref name sensitivity - any
> pointers to past discussions?
Multiple ref backend [1] should solve this.It's supposed to help
handle a huge number refs. But a side effect from not using file
system for refs is we can handle ref case-sensitivity much easier. And
I believe David had that in mind he chose lmdb (because of Mac, which
shares the same problem with Windows)
[1] http://thread.gmane.org/gmane.comp.version-control.git/281925
--
Duy
next prev parent reply other threads:[~2015-12-21 12:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 11:01 Case insensitive branch names Philip Oakley
2015-12-21 12:21 ` Duy Nguyen [this message]
2015-12-21 17:37 ` [git-for-windows] " Junio C Hamano
2015-12-21 18:22 ` Torsten Bögershausen
2015-12-21 20:08 ` Philip Oakley
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='CACsJy8CEYaf9NA4J_2u1cqsikYvtR7nz=FEiwAxsKMLSREDhCg@mail.gmail.com' \
--to=pclouds@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git-for-windows@googlegroups.com \
--cc=git@vger.kernel.org \
--cc=philipoakley@iee.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).