From: "Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: [PATCH 0/3] [Non-critical]: sparse index vs split index fixes
Date: Wed, 19 Jan 2022 17:29:36 +0000 [thread overview]
Message-ID: <pull.1119.git.1642613379.gitgitgadget@gmail.com> (raw)
We noticed split/sparse index-related issues while rebasing Microsoft's fork
of Git. These fixes are necessary for that fork's test suite to pass, but
they might not be super critical to get into upstream v2.35.0 (especially
this close to -rc2). However, the team felt that the decision should be left
to the Git maintainer whether to take these patches into v2.35.0 or not.
Johannes Schindelin (3):
sparse-index: sparse index is disallowed when split index is active
t1091: disable split index
split-index: it really is incompatible with the sparse index
read-cache.c | 3 ++
sparse-index.c | 2 +-
split-index.c | 3 ++
t/t1091-sparse-checkout-builtin.sh | 54 ++++++++++++++----------------
4 files changed, 33 insertions(+), 29 deletions(-)
base-commit: af4e5f569bc89f356eb34a9373d7f82aca6faa8a
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-1119%2Fdscho%2Fsparse-index-vs-split-index-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1119/dscho/sparse-index-vs-split-index-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/1119
--
gitgitgadget
next reply other threads:[~2022-01-19 17:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 17:29 Johannes Schindelin via GitGitGadget [this message]
2022-01-19 17:29 ` [PATCH 1/3] sparse-index: sparse index is disallowed when split index is active Johannes Schindelin via GitGitGadget
2022-01-22 1:42 ` Junio C Hamano
2022-01-22 9:30 ` Johannes Schindelin
2022-01-19 17:29 ` [PATCH 2/3] t1091: disable split index Johannes Schindelin via GitGitGadget
2022-01-19 17:29 ` [PATCH 3/3] split-index: it really is incompatible with the sparse index Johannes Schindelin via GitGitGadget
2022-01-21 23:39 ` Junio C Hamano
2022-01-22 9:32 ` Johannes Schindelin
2022-01-22 5:44 ` [PATCH 0/3] [Non-critical]: sparse index vs split index fixes Elijah Newren
2022-01-22 9:31 ` Johannes Schindelin
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.1119.git.1642613379.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmx.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 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).