user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: "Štěpán Němec" <stepnem@smrk.net>
Cc: meta@public-inbox.org
Subject: Re: [PATCH] doc/extindex: document --dedupe switch
Date: Sat, 25 Nov 2023 11:49:39 +0000	[thread overview]
Message-ID: <20231125114939.M737325@dcvr> (raw)
In-Reply-To: <20231125093637+0100.776019-stepnem@smrk.net>

Štěpán Němec <stepnem@smrk.net> wrote:
> Eric Wong wrote:
> >
> > 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?

Not MIDs, but lei has --lock= for various mbox locking methods.
cindex will also support combinations of
--join=aggressive,reset,dt:...,window:$INTEGER

I like to support commas when there's unambiguous keywords/commands
that can be easily parsed.  `dt:$approxidate' in --join could have
date-times with commas in them, but I don't think anybody would
use those characters in a command.

> > +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

  reply	other threads:[~2023-11-25 11:49 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 [this message]
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: http://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=20231125114939.M737325@dcvr \
    --to=e@80x24.org \
    --cc=meta@public-inbox.org \
    --cc=stepnem@smrk.net \
    /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).