From: Thomas Rast <trast@student.ethz.ch>
To: Junio C Hamano <gitster@pobox.com>
Cc: PJ Weisberg <pj@irregularexpressions.net>, <git@vger.kernel.org>
Subject: Re: [PATCH] Demonstrate failure of 'core.ignorecase = true'
Date: Fri, 23 Mar 2012 11:20:07 +0100 [thread overview]
Message-ID: <87pqc3ei08.fsf@thomas.inf.ethz.ch> (raw)
In-Reply-To: <7v8viswdho.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Thu, 22 Mar 2012 14:08:03 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> PJ Weisberg <pj@irregularexpressions.net> writes:
>
>> On Wed, Mar 21, 2012 at 4:58 PM, Junio C Hamano <gitster@pobox.com> wrote:
>>
>>> underlying system calls like open("foo") will *not* magically start
>>> returning a file descriptor opened for "FOO" if your filesystem is not
>>> case insensitive.
>>
>> No, but magic_open("foo") might, if someone had put forth the effort
>> to write a function called magic_open.
>
> Exactly.
>
> That is why we avoid describing what happens when you set it on a case
> sensitive filesystem, to leave the door open for such a cleverness.
>
> It may still be a mistake in the manual that we did not explicitly say
> that setting core.ignorecase on a case sensitive system will give you an
> undefined behaviour.
How about trying to read "HEAD" as "head" instead when core.ignorecase
is true? That would allow us to catch such misconfiguration (which I
imagine can also happen accidentally if you mv a repository across FS
boundaries) and tell the user about it.
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2012-03-23 10:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 22:50 [PATCH] Demonstrate failure of 'core.ignorecase = true' Peter J. Weisberg
2012-03-21 23:58 ` Junio C Hamano
2012-03-22 20:40 ` PJ Weisberg
2012-03-22 21:08 ` Junio C Hamano
2012-03-23 10:20 ` Thomas Rast [this message]
2012-03-23 17:47 ` Junio C Hamano
2012-03-23 18:48 ` Jeff King
2012-03-23 18:57 ` Jeff King
2012-03-22 6:49 ` Johannes Sixt
2012-03-22 11:25 ` Zbigniew Jędrzejewski-Szmek
2012-03-22 14:12 ` Jeff King
2012-03-22 16:57 ` Junio C Hamano
2012-03-22 17:37 ` Jeff King
2012-03-22 18:44 ` Junio C Hamano
2012-03-22 19:07 ` Jeff King
2012-03-22 20:33 ` Junio C Hamano
2012-03-22 20:00 ` Zbigniew Jędrzejewski-Szmek
2012-03-22 20:37 ` Junio C Hamano
2012-03-22 20:53 ` Zbigniew Jędrzejewski-Szmek
2012-03-22 20:55 ` PJ Weisberg
2012-03-22 21:09 ` Junio C Hamano
2012-03-22 23:00 ` Jeff King
2012-03-22 23:24 ` Junio C Hamano
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=87pqc3ei08.fsf@thomas.inf.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pj@irregularexpressions.net \
/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.