From: Wes Hardaker <wes@hardakers.net>
To: jorge.alfaro-murillo@yale.edu (Jorge A. Alfaro-Murillo)
Cc: ding@gnus.org
Subject: Re: text/plain with 80 char wrap vs the flowed mime-type (whatever it is)
Date: Tue, 02 Feb 2016 10:22:20 -0800 [thread overview]
Message-ID: <0lio27yntv.fsf@wjh.hardakers.net> (raw)
In-Reply-To: <87powmeahd.fsf@yale.edu> (Jorge A. Alfaro-Murillo's message of "Wed, 27 Jan 2016 20:52:46 -0500")
jorge.alfaro-murillo@yale.edu (Jorge A. Alfaro-Murillo) writes:
> That allows the message to be sent with format=flowed.
Thanks for your data point. I think I'll switch to that.
--
Wes Hardaker
My Pictures: http://capturedonearth.com/
My Thoughts: http://blog.capturedonearth.com/
next prev parent reply other threads:[~2016-02-02 18:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 21:59 Wes Hardaker
2016-01-28 1:52 ` Jorge A. Alfaro-Murillo
2016-02-02 18:22 ` Wes Hardaker [this message]
2016-02-04 2:54 ` Mark Simpson
2016-02-04 5:18 ` Teemu Likonen
2016-02-04 14:30 ` Teemu Likonen
2016-02-05 0:21 ` Mark Simpson
2016-02-05 17:13 ` Jorge A. Alfaro-Murillo
2016-02-04 16:17 ` Nikolaus Rath
2016-02-04 22:41 Magnus Henoch
2016-02-05 0:14 ` Nikolaus Rath
2016-02-05 0:22 ` Mark Simpson
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=0lio27yntv.fsf@wjh.hardakers.net \
--to=wes@hardakers.net \
--cc=ding@gnus.org \
--cc=jorge.alfaro-murillo@yale.edu \
/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).