From: Michael Cook <michael@waxrat.com>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: gnus-summary-resend-message and gcc
Date: Mon, 13 Feb 2012 13:39:42 -0500 [thread overview]
Message-ID: <874nuud1ch.fsf@waxrat.com> (raw)
In-Reply-To: <b4my5s7tsa0.fsf@jpl.org> (Katsumi Yamaoka's message of "Mon, 13 Feb 2012 10:51:19 +0900")
Katsumi Yamaoka <yamaoka@jpl.org> writes:
> Katsumi Yamaoka wrote:
>> Michael Cook wrote:
> [...]
>>> But gnus-agent-possibly-do-gcc calls gnus-inews-do-gcc, which
>>> seems to unconditionally do gcc.
>
>> But there should be no Gcc header in the message header then if
>> all is going right. The `message-resend' function modifies or
>> removes Gcc header according to `gnus-gcc-self-resent-messages',
>> so you can try this hook to see how the message header is then:
Turns out I had a message-header-setup-hook function that was adding
the Gcc header. That used to do what I wanted, but is apparently no
longer correct with the latest gnus. So, I've removed it.
Thanks.
Michael
next prev parent reply other threads:[~2012-02-13 18:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-11 20:21 Michael Cook
2012-02-13 1:35 ` Katsumi Yamaoka
2012-02-13 1:51 ` Katsumi Yamaoka
2012-02-13 18:39 ` Michael Cook [this message]
2012-02-13 23:38 ` Katsumi Yamaoka
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=874nuud1ch.fsf@waxrat.com \
--to=michael@waxrat.com \
--cc=ding@gnus.org \
--cc=yamaoka@jpl.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).