From: Karsten Blees <karsten.blees@gmail.com>
To: "Torsten Bögershausen" <tboegi@web.de>,
"Lee Hopkins" <leerhop@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>
Cc: Duy Nguyen <pclouds@gmail.com>,
Johannes Sixt <j.sixt@viscovery.net>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Branch Name Case Sensitivity
Date: Mon, 03 Mar 2014 11:03:33 +0100 [thread overview]
Message-ID: <53145375.4040802@gmail.com> (raw)
In-Reply-To: <53118436.5080507@web.de>
Am 01.03.2014 07:54, schrieb Torsten Bögershausen:
> On 2014-03-01 03.42, Lee Hopkins wrote:
>> +
>> + if(ignore_case)
> Only looking at ignore_case here closes the door for people
> who have a branch "foo" and "Foo" at the same time.
> (Which means that they are carefully running git pack-refs)
> How about something like this:
> + if (refs_ignore_case < 0)
> + refs_ignore_case = ignore_case;
> + if (refs_ignore_case)
I don't think this distinction is necessary, either you have a case-insensitive file system or you don't. The case that the .git directory is case-sensitive and the worktree directory isn't (or the other way around) is probably so exotic that we can ignore it.
> (And then we need the diff further down on top of this.)
> (And of course Documentation/config.txt)
> The main motivation is that you can set refs.ignorecase == true on
> e.g. Linux, to prevent to have branches "Foo" and "foo" at the same time,
> which gives problems when pulling into e.g. Windows/Mac OS
If you want to prevent problems with Windows/Mac OS, you should set core.ignorecase = true. I don't see why we need yet another config setting for refs (and logs?).
next prev parent reply other threads:[~2014-03-03 10:03 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 21:06 Branch Name Case Sensitivity Lee Hopkins
2014-02-27 19:50 ` Junio C Hamano
2014-02-27 20:32 ` Torsten Bögershausen
2014-02-27 20:37 ` Lee Hopkins
2014-02-27 21:00 ` Michael Haggerty
2014-02-27 22:24 ` Karsten Blees
2014-02-27 23:38 ` Lee Hopkins
2014-02-28 6:41 ` Johannes Sixt
2014-02-28 13:56 ` Karsten Blees
2014-02-28 14:10 ` Lee Hopkins
2014-02-28 18:58 ` Junio C Hamano
2014-02-28 23:22 ` Duy Nguyen
2014-02-28 23:28 ` Junio C Hamano
2014-03-01 2:42 ` Lee Hopkins
2014-03-01 6:54 ` Torsten Bögershausen
2014-03-01 19:38 ` Lee Hopkins
2014-03-03 10:03 ` Karsten Blees [this message]
2014-03-03 14:21 ` Lee Hopkins
2014-03-03 17:51 ` Junio C Hamano
2014-03-04 13:23 ` Karsten Blees
2014-03-04 20:37 ` Torsten Bögershausen
2014-03-05 14:02 ` Lee Hopkins
2014-02-28 9:13 ` Michael Haggerty
2014-02-28 14:31 ` Duy Nguyen
2014-02-28 14:45 ` Michael Haggerty
2014-02-28 9:11 ` Stephen Leake
2014-02-28 9:49 ` Michael Haggerty
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=53145375.4040802@gmail.com \
--to=karsten.blees@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
--cc=leerhop@gmail.com \
--cc=pclouds@gmail.com \
--cc=tboegi@web.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.