From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: Mail-Followup-To and Gmane and emacs-devel
Date: Mon, 15 May 2017 15:58:54 -0400 [thread overview]
Message-ID: <87pof9riwx.fsf@lifelogs.com> (raw)
In-Reply-To: m37f1r3vui.fsf@stories
On Mon, 08 May 2017 23:03:01 +0200 Lars Ingebrigtsen <larsi@gnus.org> wrote:
LI> I think the Gmane-Reply-To-List is the only realistic solution here for
LI> this, but you could also just split to /dev/null all mail that has both
LI> you and emacs-devel in the Cc headers.
Karl Fogel suggested letting Gnus deal with it, by suppressing duplicate
messages. Normally that only works in the same backend, but I could hook
into the gnus-registry and use it across backends. I don't know enough
of those internals, but the gnus-registry seems perfect for tracking by
message ID. Do you think that could work?
Ted
next prev parent reply other threads:[~2017-05-15 19:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170427213824.12196.63777@vcs0.savannah.gnu.org>
[not found] ` <20170427213827.B6BDC22040@vcs0.savannah.gnu.org>
2017-04-28 7:53 ` master bd60ee2 1/5: auth-source: factor out parsers and add tests Katsumi Yamaoka
2017-04-28 8:10 ` Katsumi Yamaoka
2017-04-28 12:43 ` Ted Zlatanov
2017-04-28 12:52 ` Stefan Monnier
2017-04-28 16:36 ` Glenn Morris
2017-04-28 17:12 ` Ted Zlatanov
2017-04-28 18:32 ` Stefan Monnier
2017-04-28 19:08 ` Ted Zlatanov
2017-04-28 19:28 ` Mail-Followup-To and Gmane and emacs-devel (was: master bd60ee2 1/5: auth-source: factor out parsers and add tests) Ted Zlatanov
2017-05-08 21:03 ` Mail-Followup-To and Gmane and emacs-devel Lars Ingebrigtsen
2017-05-15 19:58 ` Ted Zlatanov [this message]
2017-05-15 20:07 ` Lars Ingebrigtsen
2017-05-15 20:20 ` Ted Zlatanov
2017-04-28 22:53 ` master bd60ee2 1/5: auth-source: factor out parsers and add tests Stefan Monnier
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pof9riwx.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=emacs-devel@gnu.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://git.savannah.gnu.org/cgit/emacs.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).