All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Oakley <philipoakley@iee.email>
To: "SZEDER Gábor" <szeder.dev@gmail.com>
Cc: git@vger.kernel.org,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Emily Shaffer <emilyshaffer@google.com>
Subject: Re: [Summit topic] Let's have chalk talks (part 1/?)
Date: Tue, 26 Oct 2021 16:35:20 +0100	[thread overview]
Message-ID: <8df2fe20-1198-ad99-34ef-f9fa50a67fa2@iee.email> (raw)
In-Reply-To: <20211025222648.GD2101@szeder.dev>

On 25/10/2021 23:26, SZEDER Gábor wrote:
> On Mon, Oct 25, 2021 at 09:56:56PM +0100, Philip Oakley wrote:
>> In the meantime, while chatting to a colleague about the birthday
>> paradox and its relation to Bloom filters, I realised I didn't
>> understand what our Bloom filters were trying to do and what they recorded.
>>
>> I had a look at the code and documentation, but there isn't much there
>> about our Bloom filter implementation. A chalk talk could later be used
>> in the same manner as the packfile discussion to show what the filters do?
>>
>> If there is someone who'd like to talk through what the Bloom filters
>> are doing in Git then I'd be all ears.
> Then perhaps you might find it's worth your while to read through
> this:
>
>   https://public-inbox.org/git/20200529085038.26008-16-szeder.dev@gmail.com/
>
Thanks for the link. It's quite a size of commit message ;-)  Are there
any plans to extract the 'how it works' parts into a Bloom filter doc?

Philip

      reply	other threads:[~2021-10-26 15:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-22  7:51 [Summit topic] Let's have chalk talks (part 1/?) Johannes Schindelin
2021-10-25 20:56 ` Philip Oakley
2021-10-25 21:20   ` Ævar Arnfjörð Bjarmason
2021-10-26  9:45     ` Philip Oakley
2021-10-25 22:26   ` SZEDER Gábor
2021-10-26 15:35     ` Philip Oakley [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=8df2fe20-1198-ad99-34ef-f9fa50a67fa2@iee.email \
    --to=philipoakley@iee.email \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=emilyshaffer@google.com \
    --cc=git@vger.kernel.org \
    --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.