From: ehabkost@raisama.net (Eduardo Habkost)
Subject: [sup-talk] Handling of messages appearing on multiple sources
Date: Wed, 26 Nov 2008 19:35:23 -0200 [thread overview]
Message-ID: <20081126213523.GB4628@blackpad> (raw)
In-Reply-To: <1227647755-sup-3231@ausone.local>
On Tue, Nov 25, 2008 at 10:19:38PM +0100, Nicolas Pouillard wrote:
> Excerpts from Eduardo Habkost's message of Mon Nov 24 18:31:01 +0100 2008:
> >
> > Hi,
> Hi,
>
> > Currently, what is the expected behavior when a message appear on multiple
> > sources? Sometimes messages are sent to many different mailing lists
> > and end up on different mailboxes, and I would like those messages to
> > have the labels from both sources applied to them. Is it possible?
> >
> > It would be nice if sup-tweak-labels and other utilities that deal with
> > messages on a per-source basis were aware that the message appeared on
> > multiple sources, also.
>
> If it's the same message id, it should be shared.
When testing it here, I got the following:
Source 1 is the lkml source. Source 2 is the kvm-devel source. Some
messages are posted to both mailing lists and end up on both sources.
A message appearing only on kvm-devel is imported normally:
Adding message maildir:/home/ehabkost/mail/kvm-devel-l/#12277020930025949 with state {kvm-devel, unread, inbox}
A message appearing on both sources is imported this way:
Updating message maildir:/home/ehabkost/mail/kvm-devel-l/#12277021040004976, source 1 => 2, offset 12277036400004673 => 12277021040004976, state {lkml, unread, inbox} => {lkml, unread, inbox}
On this case, I would like the kvm-devel label to be applied to the
message, also.
I would even argue that adding the tags configured for both sources
should be the default, but I don't know if there are users relying on
the current behavior, today. What do you think?
Handling the inbox label may be more complicated to implement properly
(especially if some of the sources have the 'archive' flag set and
some don't). But as an user, I expect that a message appearing on both a
non-inbox source and an inbox source would get into the inbox. The problem
would be handling a message appearing on an inbox source after the user
have archived it. On this case, the user may expect the message to not
appear on the inbox again (I am not sure what would be more intuitive).
Additionally, I think it would be nice if sup were aware of when the
message appears multiple times on the sources, instead of rewriting the
source and offset fields. Most times the user doesn't need to be aware
there are multiple versions of a message, but when checking message
headers or other small details of messages coming from different paths,
it would be useful to have both versions available.
--
Eduardo
next prev parent reply other threads:[~2008-11-26 21:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-24 17:31 Eduardo Habkost
[not found] ` <1227647755-sup-3231@ausone.local>
2008-11-26 21:35 ` Eduardo Habkost [this message]
2008-11-26 23:31 ` William Morgan
2008-11-27 13:46 ` Eduardo Habkost
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081126213523.GB4628@blackpad \
--to=ehabkost@raisama.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox