git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, "SZEDER Gábor" <szeder.dev@gmail.com>
Subject: Re: What's cooking in git.git (Aug 2020, #03; Thu, 13)
Date: Fri, 14 Aug 2020 16:07:08 -0400	[thread overview]
Message-ID: <20200814200708.GB30103@syl.lan> (raw)
In-Reply-To: <xmqqd03u18q3.fsf@gitster.c.googlers.com>

On Thu, Aug 13, 2020 at 03:28:36PM -0700, Junio C Hamano wrote:
> * tb/bloom-improvements (2020-08-11) 14 commits
>  - builtin/commit-graph.c: introduce '--max-new-filters=<n>'
>  - commit-graph: rename 'split_commit_graph_opts'
>  - commit-graph: add large-filters bitmap chunk
>  - commit-graph.c: sort index into commits list
>  - bloom/diff: properly short-circuit on max_changes
>  - bloom: use provided 'struct bloom_filter_settings'
>  - csum-file.h: introduce 'hashwrite_be64()'
>  - bloom: split 'get_bloom_filter()' in two
>  - commit-graph.c: store maximum changed paths
>  - commit-graph: respect 'commitGraph.readChangedPaths'
>  - t/helper/test-read-graph.c: prepare repo settings
>  - commit-graph: pass a 'struct repository *' in more places
>  - t4216: use an '&&'-chain
>  - commit-graph: introduce 'get_bloom_filter_settings()'
>
>  Misc Bloom filter improvements.
>
>  Expecting a reroll.
>  It seems that the review is getting closer to result in another update.
>  cf. <20200811220503.GC66656@syl.lan>

Yep, I am planning on a re-roll sometime early or mid-next week. I would
really like to avoid another one after that, so I'm hoping that all of
the review can settle before then.

Thanks,
Taylor

  reply	other threads:[~2020-08-14 20:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-13 22:28 Junio C Hamano
2020-08-14 20:07 ` Taylor Blau [this message]
2020-08-15  7:14 ` René Scharfe

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200814200708.GB30103@syl.lan \
    --to=me@ttaylorr.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=szeder.dev@gmail.com \
    --subject='Re: What'\''s cooking in git.git (Aug 2020, #03; Thu, 13)' \
    /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

Code repositories for project(s) associated with this inbox:

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).