All of lore.kernel.org
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: "SZEDER Gábor" <szeder.dev@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2023, #05; Fri, 15)
Date: Mon, 25 Sep 2023 19:06:21 -0400	[thread overview]
Message-ID: <ZRISbdyy1OhcOKgj@nand.local> (raw)
In-Reply-To: <20230924195900.GA1156862@szeder.dev>

On Sun, Sep 24, 2023 at 09:59:00PM +0200, SZEDER Gábor wrote:
> Besides the issue of not reading Bloom filter for root commits, that
> message of mine also includes a test demonstrating that handling split
> commit graph with layers containing different versions of Bloom
> filters is broken.  That test still fails with the current version of
> this patch series, i.e. what is currently in seen.  Jonathan provided
> a patch that makes that test pass, and also noted that that test did
> pass with his original design:
>
>   https://public-inbox.org/git/20230901205616.3572722-1-jonathantanmy@google.com/

I am not sure whether you are pointing out an existing breakage which
remains unfixed, or pointing out a new bug introduced by this series. I
think that it is the former, but I wrote up some of my confusion in:

  https://lore.kernel.org/git/ZRIRtlbsYadg7EUx@nand.local/

> I maintain that without test cases thoroughly covering the interaction
> of different Bloom filter versions with split commit graphs this
> series should not be merged.

Agreed. We should wait for the discussion in the linked thread to settle
before merging this down.

Thanks,
Taylor

  reply	other threads:[~2023-09-25 23:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-16  1:41 What's cooking in git.git (Sep 2023, #05; Fri, 15) Junio C Hamano
2023-09-19 18:32 ` Taylor Blau
2023-09-24 19:59   ` SZEDER Gábor
2023-09-25 23:06     ` Taylor Blau [this message]
2023-09-19 20:00 ` Linus Arver
2023-09-19 20:16   ` Junio C Hamano
2023-09-19 21:25   ` Junio C Hamano
2023-09-20  6:37     ` Linus Arver
2023-09-20 14:57       ` Junio C Hamano
2023-09-20 19:20         ` Linus Arver

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=ZRISbdyy1OhcOKgj@nand.local \
    --to=me@ttaylorr.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=szeder.dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.