From: Derrick Stolee <derrickstolee@github.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (May 2023, #02; Fri, 5)
Date: Mon, 8 May 2023 16:59:49 -0400 [thread overview]
Message-ID: <cfb5fe88-d270-62e3-01f8-ac53049ebb63@github.com> (raw)
In-Reply-To: <xmqqmt2ibcq2.fsf@gitster.g>
On 5/5/2023 7:05 PM, Junio C Hamano wrote:
> * ds/fsck-bitmap (2023-05-02) 2 commits
> - fsck: use local repository
> - fsck: verify checksums of all .bitmap files
>
> "git fsck" learned to detect bit-flip breakages in the reachability
> bitmap files.
>
> Will merge to 'master'.
> source: <pull.1526.v2.git.1683034042.gitgitgadget@gmail.com>
This has been marked as "Will merge to 'master'" for a few cooking
emails, but as far as I can tell it hasn't even hit 'next'. Is
there a reason for that?
Thanks,
-Stolee
next prev parent reply other threads:[~2023-05-08 21:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 23:05 What's cooking in git.git (May 2023, #02; Fri, 5) Junio C Hamano
2023-05-08 7:31 ` ps/fetch-output-format (was: What's cooking in git.git (May 2023, #02; Fri, 5)) Patrick Steinhardt
2023-05-08 16:38 ` What's cooking in git.git (May 2023, #02; Fri, 5) Felipe Contreras
2023-05-08 20:59 ` Derrick Stolee [this message]
2023-05-08 21:40 ` 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=cfb5fe88-d270-62e3-01f8-ac53049ebb63@github.com \
--to=derrickstolee@github.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).