From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>, Madhu <enometh@meer.net>
Cc: ozhap@vollbio.de, 43356@debbugs.gnu.org, help-gnu-emacs@gnu.org
Subject: bug#43356: Gnus: caching message headers? bug#43356
Date: Thu, 15 Oct 2020 22:44:11 -0700 (PDT) [thread overview]
Message-ID: <b41ee6c5-8d0f-4491-a61e-5650bb272e71__16302.2303184093$1602827233$gmane$org@default> (raw)
In-Reply-To: <87blh2sq3u.fsf@gnus.org>
Please don't post the same message to both the bug list and the help-gnu-emacs mailing list. Thx.
next prev parent reply other threads:[~2020-10-16 5:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87v9flz99u.fsf@vollbio.de>
2020-10-15 12:23 ` bug#43356: Gnus: caching message headers? bug#43356 Madhu
2020-10-16 5:21 ` Lars Ingebrigtsen
2020-10-16 5:44 ` Drew Adams [this message]
2020-10-17 10:09 ` Ozhap
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='b41ee6c5-8d0f-4491-a61e-5650bb272e71__16302.2303184093$1602827233$gmane$org@default' \
--to=drew.adams@oracle.com \
--cc=43356@debbugs.gnu.org \
--cc=enometh@meer.net \
--cc=help-gnu-emacs@gnu.org \
--cc=larsi@gnus.org \
--cc=ozhap@vollbio.de \
/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).