From: "Derrick Stolee via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: szeder.dev@gmail.com, newren@gmail.com,
Derrick Stolee <dstolee@microsoft.com>,
Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 0/1] sparse-checkout: respect core.ignoreCase in cone mode
Date: Mon, 09 Dec 2019 19:42:59 +0000 [thread overview]
Message-ID: <pull.488.git.1575920580.gitgitgadget@gmail.com> (raw)
This is the first of several cleanups to the sparse-checkout feature that
had a large overhaul in ds/sparse-cone.
We have an internal customer that plans to use sparse-checkout as a core
feature of their version control experience. They use a case-insensitive
filesystem, so as they created their directory dependency graph they did not
keep consistent casing. This data is what they plan to feed to "git
sparse-checkout set".
While I would certainly prefer that the data is cleaned up (and that process
is ongoing), I could not argue with the logic that git add does the "right
thing" when core.ignoreCase is enabled.
Thanks, -Stolee
Derrick Stolee (1):
sparse-checkout: respect core.ignoreCase in cone mode
Documentation/git-sparse-checkout.txt | 4 ++++
builtin/sparse-checkout.c | 19 +++++++++++++++++--
cache.h | 1 +
name-hash.c | 10 ++++++++++
t/t1091-sparse-checkout-builtin.sh | 13 +++++++++++++
5 files changed, 45 insertions(+), 2 deletions(-)
base-commit: cff4e9138d8df45e3b6199171092ee781cdadaeb
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-488%2Fderrickstolee%2Fsparse-case-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-488/derrickstolee/sparse-case-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/488
--
gitgitgadget
next reply other threads:[~2019-12-09 19:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 19:42 Derrick Stolee via GitGitGadget [this message]
2019-12-09 19:43 ` [PATCH 1/1] sparse-checkout: respect core.ignoreCase in cone mode Derrick Stolee via GitGitGadget
2019-12-11 18:44 ` Junio C Hamano
2019-12-11 19:11 ` Derrick Stolee
2019-12-11 20:00 ` Junio C Hamano
2019-12-11 20:29 ` Derrick Stolee
2019-12-11 21:37 ` Junio C Hamano
2019-12-12 2:51 ` Derrick Stolee
2019-12-12 20:59 ` Derrick Stolee
2019-12-13 19:05 ` Junio C Hamano
2019-12-13 19:40 ` Derrick Stolee
2019-12-13 22:02 ` Junio C Hamano
2019-12-13 18:09 ` [PATCH v2 0/1] " Derrick Stolee via GitGitGadget
2019-12-13 18:09 ` [PATCH v2 1/1] " Derrick Stolee via GitGitGadget
2019-12-13 19:58 ` [PATCH v2 0/1] " Junio C Hamano
2019-12-18 11:41 ` [PATCH " Ed Maste
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=pull.488.git.1575920580.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=dstolee@microsoft.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=newren@gmail.com \
--cc=szeder.dev@gmail.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 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.