From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: The new registry errors when spam.el is moving messages
Date: Fri, 22 Apr 2011 08:09:39 +0900 [thread overview]
Message-ID: <b4mbozz9p70.fsf@jpl.org> (raw)
In-Reply-To: <878vv3qrjw.fsf@lifelogs.com>
Ted Zlatanov <tzz@lifelogs.com> wrote:
[...]
> I fixed this: we need to use the extra header slot (`mail-header-extra')
> and that's an alist of headers. But the user needs to add To and Cc to
> `gnus-extra-headers', so I explained that in the package commentary.
Oh, I realized gnus-registry.el is not incomplete. Sorry for my
having been rudeness.
> I actually think To and Cc should be in `gnus-extra-headers' by default.
> Is there any reason not to add them? The extra memory usage is
> negligible.
That's reasonable. Please do it.
[...]
> Fortunately I think we're OK now.
I believe it. Thanks for your work.
next prev parent reply other threads:[~2011-04-21 23:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 10:04 Tassilo Horn
2011-04-20 10:56 ` Tassilo Horn
2011-04-20 13:01 ` Katsumi Yamaoka
2011-04-20 18:34 ` Ted Zlatanov
2011-04-21 0:05 ` Katsumi Yamaoka
2011-04-21 20:26 ` Ted Zlatanov
2011-04-21 23:09 ` Katsumi Yamaoka [this message]
2011-04-21 23:26 ` Ted Zlatanov
2011-04-20 20:55 ` Ted Zlatanov
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=b4mbozz9p70.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).