From: Johannes Sixt <j6t@kdbg.org>
To: Robert Buck <buck.robert.j@gmail.com>
Cc: git@vger.kernel.org, Joshua Jensen <jjensen@workspacewhiz.com>
Subject: Re: [PATCH 0/6] Extensions of core.ignorecase=true support
Date: Tue, 17 Aug 2010 23:20:17 +0200 [thread overview]
Message-ID: <201008172320.17939.j6t@kdbg.org> (raw)
In-Reply-To: <AANLkTi=0j_JFWBp=kJG6v+YBUxKAiVAVc4UtG0LWmipq@mail.gmail.com>
On Dienstag, 17. August 2010, Robert Buck wrote:
> While I tend to agree with case-insensitive searches, I would tend to
> question the use of a non-case-preserving / last-use methodology
> reminiscent of the days of DOS.
There is no "last-use" involved. Everything's rather "first-use", i.e.,
case-preserving.
> The nice thing about case-insensitivity is that when requesting a file
> by name any capitalization can be used. The bad thing, well come to
> think of it, there is none that I can think of, but for those more
> religious than I about Unix they may cite otherwise.
What do you mean by "requesting a file"?
core.ignorecase is purely about the worktree and the transition of files from
the worktree to the index. It is *not* involved when files are moved from the
index or the repository to the worktree. In particular, it is not used when
you give a pathspec to limit 'git log' results. (Joshua proposed a change
where core.ignorecase would also kick in in this case as well, but this
change is not included in this series, and I would not agree to it.)
-- Hannes
next prev parent reply other threads:[~2010-08-17 21:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-16 19:38 [PATCH 0/6] Extensions of core.ignorecase=true support Johannes Sixt
2010-08-16 19:38 ` [PATCH 1/6] Add string comparison functions that respect the ignore_case variable Johannes Sixt
2010-08-18 12:52 ` Ævar Arnfjörð Bjarmason
2010-08-18 12:53 ` Ævar Arnfjörð Bjarmason
2010-08-18 15:52 ` Joshua Jensen
2010-08-18 16:07 ` Ævar Arnfjörð Bjarmason
2010-08-18 18:32 ` Johannes Sixt
2010-08-18 18:58 ` Ævar Arnfjörð Bjarmason
2010-08-29 19:39 ` Ævar Arnfjörð Bjarmason
2010-08-30 14:42 ` Joshua Jensen
2010-08-30 14:51 ` Ævar Arnfjörð Bjarmason
2010-08-30 15:05 ` Jonathan Nieder
2010-08-30 14:52 ` Jonathan Nieder
2010-08-30 18:40 ` Johannes Sixt
2010-08-30 19:57 ` Ævar Arnfjörð Bjarmason
2010-08-30 20:13 ` Johannes Sixt
2010-08-16 19:38 ` [PATCH 2/6] Case insensitivity support for .gitignore via core.ignorecase Johannes Sixt
2010-08-16 19:38 ` [PATCH 3/6] Add case insensitivity support for directories when using git status Johannes Sixt
2010-08-16 19:38 ` [PATCH 4/6] Add case insensitivity support when using git ls-files Johannes Sixt
2010-08-16 19:38 ` [PATCH 5/6] Support case folding for git add when core.ignorecase=true Johannes Sixt
2010-08-16 19:38 ` [PATCH 6/6] Support case folding in git fast-import " Johannes Sixt
2010-08-17 19:36 ` [PATCH 0/6] Extensions of core.ignorecase=true support Robert Buck
2010-08-17 21:20 ` Johannes Sixt [this message]
2010-08-18 2:41 ` Robert Buck
2010-08-18 18:31 ` Johannes Sixt
2010-08-22 7:23 ` 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=201008172320.17939.j6t@kdbg.org \
--to=j6t@kdbg.org \
--cc=buck.robert.j@gmail.com \
--cc=git@vger.kernel.org \
--cc=jjensen@workspacewhiz.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.
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 NNTP newsgroup(s).