From: NAKAJI Hiroyuki <nakaji@jp.freebsd.org>
To: ding@gnus.org
Subject: Re: " =20" at the end of line
Date: Wed, 19 Sep 2007 00:02:36 +0900 [thread overview]
Message-ID: <86ir68m2yb.fsf@ra333.heimat.gr.jp> (raw)
In-Reply-To: <87abrkcl4y.fsf@roddy.4407.kankyo-u.ac.jp> (NAKAJI Hiroyuki's message of "Tue, 18 Sep 2007 19:39:57 +0900")
>>>>> In <87abrkcl4y.fsf@roddy.4407.kankyo-u.ac.jp>
>>>>> NAKAJI Hiroyuki <nakaji@jp.FreeBSD.org> wrote:
> > What type did you choose? I haven't tried `Plain Text' yet but
> > I guess `MIME' is better.
> My selection was `Plain Text', because I subscribed the list before it
> started using mailman and there was no choice. I've changed it to `MIME'
> to observe the difference.
OK, `MIME' digest mail does not have this problem. Thanks.
--
NAKAJI Hiroyuki
next prev parent reply other threads:[~2007-09-18 15:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-14 12:54 NAKAJI Hiroyuki
2007-09-18 10:10 ` Katsumi Yamaoka
2007-09-18 10:39 ` NAKAJI Hiroyuki
2007-09-18 15:02 ` NAKAJI Hiroyuki [this message]
2007-09-18 23:14 ` Katsumi Yamaoka
2007-09-19 0:14 ` NAKAJI Hiroyuki
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=86ir68m2yb.fsf@ra333.heimat.gr.jp \
--to=nakaji@jp.freebsd.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).