user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <>
Subject: Re: [PATCH 3/4] content_hash: normalize whitespace before hashing addresses
Date: Tue, 5 Oct 2021 07:09:18 +0000	[thread overview]
Message-ID: <20211005070918.GA13812@dcvr> (raw)
In-Reply-To: <>

Eric Wong <> wrote:
> This should prevent some false duplicates.  I noticed this
> while implementing "lei mail-diff", and only noticed it when
> I implemented the ContentDigestDbg wrapper for mail-diff.

Btw, I completely forgot -extindex has a --dedupe switch
for dealing with situations like this:

	public-inbox-extindex --dedupe=MSGID [--dedupe=MSGID1]
	public-inbox-extindex --dedupe # everything!

It looks like there's even test cases for it in t/extsearch.t (!)

I'm running --dedupe on, because apparently
--reindex doesn't deduplicate :x

And there's a lot of stuff I still need to document in
the pod/manpage :x

  reply	other threads:[~2021-10-05  7:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-02 11:18 [PATCH 0/4] lei mail-diff and other small things Eric Wong
2021-10-02 11:18 ` [PATCH 1/4] extsearchidx: attach_config: set {ibx_map} value to $ibx Eric Wong
2021-10-02 11:18 ` [PATCH 2/4] lei mail-diff: diagnostic command to diff mail contents Eric Wong
2021-10-02 11:18 ` [PATCH 3/4] content_hash: normalize whitespace before hashing addresses Eric Wong
2021-10-05  7:09   ` Eric Wong [this message]
2021-10-02 11:18 ` [PATCH 4/4] extsearchidx: emit diagnostics for missing blobs Eric Wong

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:

  List information:

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

  git send-email \
    --in-reply-to=20211005070918.GA13812@dcvr \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

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).