user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: thoughts improving duplicate message handling...
Date: Tue, 29 Dec 2020 10:50:15 -0500	[thread overview]
Message-ID: <20201229155015.w5tis6i3hr4pz3lo@chatter.i7.local> (raw)
In-Reply-To: <20201228214146.GB17600@dcvr>

On Mon, Dec 28, 2020 at 09:41:46PM +0000, Eric Wong wrote:
> a) There are occasionally resent revisions of patches with the
>    same Message-ID

This is broken and is unwanted. :)

> b) More often, a cross-posted message has different trailers
>    depending on which list it was posted to.  (And the
>    PublicInbox::Filter::* API doesn't apply at indexing,
>    only at git injection time)

In this case, my preferred solution is "first in wins", with ability to affect
which one shows up first, using a weighting metric such as "comes first in the
config file" or "has a higher priority setting."

-K

      reply	other threads:[~2020-12-29 15:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-28 21:41 thoughts improving duplicate message handling Eric Wong
2020-12-29 15:50 ` Konstantin Ryabitsev [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=20201229155015.w5tis6i3hr4pz3lo@chatter.i7.local \
    --to=konstantin@linuxfoundation.org \
    --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).