From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: Ugly In-Reply-To?
Date: Fri, 11 May 2007 09:22:49 +0900 [thread overview]
Message-ID: <b4mabwcdx9i.fsf@jpl.org> (raw)
In-Reply-To: <b4m6470fc68.fsf@jpl.org> (Katsumi Yamaoka's message of "Fri, 11 May 2007 09:15:27 +0900")
>>>>> In <b4m6470fc68.fsf@jpl.org> Katsumi Yamaoka wrote:
> However, there is a special example. If the original message
> has no header containing Message-IDs, 'message-make-in-reply-to'
> will create the In-Reply-To header like the following:
In-Reply-To: (Foo Bar's message of "Mon, 7 May 2007 14:46:18 +0200")
(Sorry, my `message-send-mail-hook' removed this in the last message.)
> I don't know whether we can say such one is a structured header
> like To or From, but Gnus still quotes tspecial characters in it
> because there is no parenthesis. It only makes it ugly.
next prev parent reply other threads:[~2007-05-11 0:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-07 12:51 Simon Josefsson
2007-05-10 1:21 ` Katsumi Yamaoka
2007-05-10 2:27 ` Miles Bader
2007-05-10 19:55 ` Reiner Steib
2007-05-11 0:15 ` Katsumi Yamaoka
2007-05-11 0:22 ` Katsumi Yamaoka [this message]
2007-05-11 0:28 ` 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=b4mabwcdx9i.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).