From: Taylor Blau <me@ttaylorr.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: tb/midx-bitmap-corruption-fix
Date: Sat, 11 Dec 2021 17:09:43 -0500 [thread overview]
Message-ID: <YbUhp2OnD7gVEGJm@nand.local> (raw)
In-Reply-To: <xmqqilvvluoa.fsf@gitster.g>
On Fri, Dec 10, 2021 at 06:52:37PM -0800, Junio C Hamano wrote:
> * tb/midx-bitmap-corruption-fix (2021-12-08) 2 commits
> - midx.c: make changing the preferred pack safe
> - t5326: demonstrate bitmap corruption after permutation
>
> A bug that made multi-pack bitmap and the object order out-of-sync
> (hence the .midx data gets corrupted) has been fixed.
>
> Will merge to 'next'?
> source: <cover.1638991570.git.me@ttaylorr.com>
Let's wait. The patch does fix the bug, but somewhat accidentally. I
have a few proposed directions in the discussion beginning at:
https://lore.kernel.org/git/YbOeEjNic5ETGcdy@nand.local/
but I want to hear from others before deciding on a direction.
Thanks,
Taylor
next prev parent reply other threads:[~2021-12-11 22:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-11 2:52 What's cooking in git.git (Dec 2021, #03; Fri, 10) Junio C Hamano
2021-12-11 3:44 ` ns/batched-fsync and ns/remerge-diff Neeraj Singh
2021-12-11 6:38 ` Elijah Newren
2021-12-11 8:39 ` What's cooking in git.git (Dec 2021, #03; Fri, 10) Eric Sunshine
2021-12-13 19:08 ` Junio C Hamano
2021-12-11 10:49 ` Elijah Newren
2021-12-13 18:28 ` Junio C Hamano
2021-12-15 18:47 ` Junio C Hamano
2021-12-11 22:09 ` Taylor Blau [this message]
2021-12-15 18:47 ` tb/midx-bitmap-corruption-fix Junio C Hamano
2021-12-12 18:37 ` ab/common-main-cleanup (was: What's cooking in git.git (Dec 2021, #03; Fri, 10)) Ævar Arnfjörð Bjarmason
2021-12-12 18:41 ` ab/only-single-progress-at-once " Ævar Arnfjörð Bjarmason
2021-12-13 4:44 ` ab/only-single-progress-at-once Junio C Hamano
2021-12-12 22:42 ` ms/customizable-ident-expansion (was: What's cooking in git.git (Dec 2021, #03; Fri, 10)) Ævar Arnfjörð Bjarmason
2021-12-13 9:02 ` ms/customizable-ident-expansion Junio C Hamano
2021-12-13 15:32 ` What's cooking in git.git (Dec 2021, #03; Fri, 10) Jeff Hostetler
2021-12-13 15:39 ` Jeff Hostetler
2021-12-14 10:59 ` 'Re: What's cooking in git.git (Dec 2021, #03; Fri, 10)' Teng Long
2021-12-15 18:53 ` Junio C Hamano
2021-12-15 11:10 ` What's cooking in git.git (Dec 2021, #03; Fri, 10) Phillip Wood
2021-12-15 18:54 ` Junio C Hamano
2022-01-04 3:46 What's cooking in git.git (Jan 2022, #01; Mon, 3) Junio C Hamano
2022-01-04 17:32 ` tb/midx-bitmap-corruption-fix (was: What's cooking in git.git (Jan 2022, #01; Mon, 3)) Taylor Blau
2022-01-04 20:13 ` tb/midx-bitmap-corruption-fix 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=YbUhp2OnD7gVEGJm@nand.local \
--to=me@ttaylorr.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).