From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Reuben Hawkins <reubenhwk@gmail.com>,
git@vger.kernel.org, dpotapov@gmail.com, tboegi@web.de,
Joshua Jensen <jjensen@workspacewhiz.com>
Subject: Re: [PATCH] fast-import.c: always honor the filename case
Date: Mon, 03 Feb 2014 09:21:29 -0800 [thread overview]
Message-ID: <xmqqvbwwf6xy.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20140202230038.GB16196@sigill.intra.peff.net> (Jeff King's message of "Sun, 2 Feb 2014 18:00:38 -0500")
Jeff King <peff@peff.net> writes:
> [+cc Joshua Jensen, who wrote 50906e0]
>
> On Sun, Feb 02, 2014 at 07:13:04AM -0600, Reuben Hawkins wrote:
>
>> fast-import should not use strncmp_icase.
>
> I am not sure of that. My gut feeling is that core.ignorecase is
> completely about the _filesystem_, and that git should generally be
> case-sensitive internally.
I agree; if squashing mixed cases into a single canonical one is
desired in one use case (like Joshua described in $gmane/200597),
that should have been done as an optional feature, not by default
(ideally, it should probably be done in a filter between exporters
and the fast-import, I would think).
> [1] I am mostly trying to connect people on various sides of the
> discussion here. So take my "gut feeling" above with a grain of
> salt, as it does not come from experience nor thinking too hard
> about the issue.
Thanks; that is exactly what is expected of project elders ;-)
prev parent reply other threads:[~2014-02-03 17:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-02 13:13 [PATCH] fast-import.c: always honor the filename case Reuben Hawkins
2014-02-02 20:08 ` Torsten Bögershausen
[not found] ` <CAD_8n+RZACW0380co75gWSwVmCJdcH4COsySTF3BFCyKEumXNA@mail.gmail.com>
2014-02-03 20:21 ` Torsten Bögershausen
2014-02-04 0:14 ` Junio C Hamano
[not found] ` <CAD_8n+RuwQEXJRCOr+B_PqA7z6LkFdbcRZkiiVJsEhJ=+YjRDg@mail.gmail.com>
2014-02-05 21:19 ` Torsten Bögershausen
[not found] ` <CAD_8n+Thn3tNTYxLK49mDOGdLpWRCFUCJo9b76UbAjnCdqXsRQ@mail.gmail.com>
2014-02-09 20:34 ` Torsten Bögershausen
[not found] ` <CAD_8n+ToUDbXrVuru7GV7toYKHXuQb8vL3B_-sfzQdXZFqzD2A@mail.gmail.com>
2014-02-11 17:29 ` Torsten Bögershausen
2014-02-02 23:00 ` Jeff King
2014-02-03 17:21 ` Junio C Hamano [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=xmqqvbwwf6xy.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=dpotapov@gmail.com \
--cc=git@vger.kernel.org \
--cc=jjensen@workspacewhiz.com \
--cc=peff@peff.net \
--cc=reubenhwk@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.
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).