From: "SZEDER Gábor" <szeder.dev@gmail.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Jonathan Tan <jonathantanmy@google.com>,
Elijah Newren <newren@gmail.com>,
git@vger.kernel.org
Subject: Re: What's cooking in git.git (Oct 2023, #04; Tue, 10)
Date: Thu, 19 Oct 2023 19:00:02 +0200 [thread overview]
Message-ID: <20231019170002.GA9904@szeder.dev> (raw)
In-Reply-To: <ZSb292VxDQoeSu2o@nand.local>
On Wed, Oct 11, 2023 at 03:26:47PM -0400, Taylor Blau wrote:
> On Tue, Oct 10, 2023 at 06:32:16PM -0700, Junio C Hamano wrote:
> > * tb/path-filter-fix (2023-08-30) 15 commits
> > - bloom: introduce `deinit_bloom_filters()`
> > - commit-graph: reuse existing Bloom filters where possible
> > - object.h: fix mis-aligned flag bits table
> > - commit-graph: drop unnecessary `graph_read_bloom_data_context`
> > - commit-graph.c: unconditionally load Bloom filters
> > - t/t4216-log-bloom.sh: harden `test_bloom_filters_not_used()`
> > - bloom: prepare to discard incompatible Bloom filters
> > - bloom: annotate filters with hash version
> > - commit-graph: new filter ver. that fixes murmur3
> > - repo-settings: introduce commitgraph.changedPathsVersion
> > - t4216: test changed path filters with high bit paths
> > - t/helper/test-read-graph: implement `bloom-filters` mode
> > - bloom.h: make `load_bloom_filter_from_graph()` public
> > - t/helper/test-read-graph.c: extract `dump_graph_info()`
> > - gitformat-commit-graph: describe version 2 of BDAT
> >
> > The Bloom filter used for path limited history traversal was broken
> > on systems whose "char" is unsigned; update the implementation and
> > bump the format version to 2.
> >
> > Reroll exists, not picked up yet.
> > cf. <20230830200218.GA5147@szeder.dev>
> > cf. <20230901205616.3572722-1-jonathantanmy@google.com>
> > cf. <20230924195900.GA1156862@szeder.dev>
> > cf. <20231008143523.GA18858@szeder.dev>
> > source: <cover.1693413637.git.jonathantanmy@google.com>
>
> Great, thanks for noting that you saw it ;-). I think that this one is
> ready to go, but I'm obviously biased and I'd feel better if Jonathan or
> Gábor (both CC'd) would take a look before you merge this down.
The test I posted in 20230830200218.GA5147@szeder.dev checking
different Bloom filter versions in different commit-graph layers still
fails in current seen.
prev parent reply other threads:[~2023-10-19 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 1:32 What's cooking in git.git (Oct 2023, #04; Tue, 10) Junio C Hamano
2023-10-11 19:26 ` Taylor Blau
2023-10-19 17:00 ` SZEDER Gábor [this message]
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=20231019170002.GA9904@szeder.dev \
--to=szeder.dev@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jonathantanmy@google.com \
--cc=me@ttaylorr.com \
--cc=newren@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 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).