From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stepnem@smrk.net>
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-ASN: AS20473 45.76.80.0/20
X-Spam-Status: No, score=-3.2 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_NONE,SPF_PASS,
	T_SCC_BODY_TEXT_LINE shortcircuit=no autolearn=ham autolearn_force=no
	version=3.4.6
Received: from mail.smrk.net (mail.smrk.net [45.76.87.244])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA512)
	(No client certificate requested)
	by dcvr.yhbt.net (Postfix) with ESMTPS id DDA821F406
	for <meta@public-inbox.org>; Sat, 25 Nov 2023 08:36:40 +0000 (UTC)
Authentication-Results: dcvr.yhbt.net;
	dkim=pass (2048-bit key; unprotected) header.d=smrk.net header.i=@smrk.net header.a=rsa-sha256 header.s=20221002 header.b=MxpdPaE4;
	dkim-atps=neutral
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=smrk.net; s=20221002;
	t=1700901398;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:cc:mime-version:mime-version:content-type:content-type:
	 content-transfer-encoding:content-transfer-encoding:
	 in-reply-to:in-reply-to:references:references;
	bh=ea7FIUaA+kKPPGR9bhXOlbpH5XqoKEVQPc/BrxUzpQA=;
	b=MxpdPaE4lbC7E460R5d67/h9f/j1i0A63q2v3zKoAHRAM6p/4kWdjA0d0mG5ipBhIXhCnM
	lVhNLwqdibURVqYKFBHRCsb/kDBzZ5wzdMRWU0ZthArpzfzus3PSLdacMtcdI8Fo3zCpbd
	D6h3uvfAh2nfLcJVJ+uw9thsUDnQvD+OkGY6fTkngCOw2hpRbObVYPnwYlSPbbSBgXW07G
	zxuxuet5wIBejIt8wMLXwS8aSjct6FC2a6N/IZ07XnVT6A4es8apOOmxe5GI3S3Piji+sF
	ulFdSscdVEEZIF20/R8KMym5tCHzOInAsuqf6n9e1WBGq8KNDpDqyZnxCcvyfQ==
Received: from localhost (<unknown> [192.168.5.2])
	by smrk (OpenSMTPD) with ESMTPSA id 84be2b10 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO);
	Sat, 25 Nov 2023 09:36:38 +0100 (CET)
From: =?utf-8?B?xaB0xJtww6FuIE7Em21lYw==?= <stepnem@smrk.net>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: [PATCH] doc/extindex: document --dedupe switch
In-Reply-To: <20231124235829.M382392@dcvr> (Eric Wong's message of "Fri, 24
	Nov 2023 23:58:29 +0000")
References: <20231124041819.1979651-1-e@80x24.org>
	<20231124135059+0100.879284-stepnem@smrk.net>
	<20231124235829.M382392@dcvr>
User-Agent: Gnus/5.13 (Gnus v5.13)
Date: Sat, 25 Nov 2023 09:36:37 +0100
Message-ID: <20231125093637+0100.776019-stepnem@smrk.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
List-Id: <meta.public-inbox.org>

On Fri, 24 Nov 2023 23:58:29 +0000
Eric Wong wrote:

>> > +Rerun deduplication on messages of a Message-IDs or all messages
>>                                    ^^^^^^^^^^^^^^^^
>> "with the given Message-ID"?  (or just drop the trailing "s")
>
> Yes, the former, thanks.
>
> I'm also wondering if it's necessary to have a blurb about NOT
> supporting comma-delimited Message-IDs on the CLI, since some
> strange Message-IDs may have a comma in them.

I think the description is already quite clear on that,
esp. given the subsequent "may be specified multiple times
...".  But the "on the CLI" qualification intrigues me: does
that mean that comma-delimited MIDs _are_ supported
somewhere else?

> Anyways, I'll squash something like this in:

[...]

> +Rerun deduplication on messages of with the given Message-ID or
                                   ^^^^^^^
not so fast :-P

> +all messages if no Message-ID is specified.  Deduplication rules may
> +change and evolve over time, especially if filters are involved.
>=20=20
>  C<--dedupe=3DMSGID> may be specified multiple times to deduplicate
>  multiple Message-IDs.

Thanks,

  =C5=A0t=C4=9Bp=C3=A1n