From: "Štěpán Němec" <stepnem@smrk.net>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: [PATCH] doc/extindex: document --dedupe switch
Date: Sat, 25 Nov 2023 22:35:16 +0100 [thread overview]
Message-ID: <20231125223516+0100.263029-stepnem@smrk.net> (raw)
In-Reply-To: <20231125114939.M737325@dcvr> (Eric Wong's message of "Sat, 25 Nov 2023 11:49:39 +0000, Sat, 25 Nov 2023 20:25:20 +0000")
On Sat, 25 Nov 2023 11:49:39 +0000
Eric Wong wrote:
>> ...". But the "on the CLI" qualification intrigues me: does
>> that mean that comma-delimited MIDs _are_ supported
>> somewhere else?
>
> Not MIDs, but lei has --lock= for various mbox locking methods.
> cindex will also support combinations of
> --join=aggressive,reset,dt:...,window:$INTEGER
I see, thanks.
On Sat, 25 Nov 2023 20:25:20 +0000
Eric Wong wrote:
> Eric Wong <e@80x24.org> wrote:
>> Štěpán Němec <stepnem@smrk.net> wrote:
>> > Eric Wong wrote:
>> > > +Rerun deduplication on messages of with the given Message-ID or
>> > ^^^^^^^
>> > not so fast :-P
>>
>> Thanks. Will s/of // when I commit when more awake.
>> Getting even more scatter-brained :x
>
> OK, will probably push this out:
>
> --------8<--------
> Subject: [PATCH] doc/extindex: document --dedupe switch
>
> We've had it since v1.7.0 when -extindex was introduced,
> but it was never documented outside of commit messages.
> ---
> Documentation/public-inbox-extindex.pod | 26 +++++++++++++++++++++----
> 1 file changed, 22 insertions(+), 4 deletions(-)
LGTM
--
Štěpán
prev parent reply other threads:[~2023-11-25 21:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 4:18 [PATCH] doc/extindex: document --dedupe switch Eric Wong
2023-11-24 12:50 ` Štěpán Němec
2023-11-24 23:58 ` Eric Wong
2023-11-25 8:36 ` Štěpán Němec
2023-11-25 11:49 ` Eric Wong
2023-11-25 20:25 ` [PATCH v3] " Eric Wong
2023-11-25 21:35 ` Štěpán Němec [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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231125223516+0100.263029-stepnem@smrk.net \
--to=stepnem@smrk.net \
--cc=e@80x24.org \
--cc=meta@public-inbox.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).