user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
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 09:36:37 +0100	[thread overview]
Message-ID: <20231125093637+0100.776019-stepnem@smrk.net> (raw)
In-Reply-To: <20231124235829.M382392@dcvr> (Eric Wong's message of "Fri, 24 Nov 2023 23:58:29 +0000")

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.
>  
>  C<--dedupe=MSGID> may be specified multiple times to deduplicate
>  multiple Message-IDs.

Thanks,

  Štěpán

  reply	other threads:[~2023-11-25  8:36 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 [this message]
2023-11-25 11:49       ` Eric Wong
2023-11-25 20:25         ` [PATCH v3] " Eric Wong
2023-11-25 21:35         ` [PATCH] " Štěpán Němec

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

	https://80x24.org/public-inbox.git

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