From: ron minnich <rminnich@gmail.com>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: [TUHS] RFC formatting
Date: Fri, 4 Oct 2019 15:41:30 -0700 [thread overview]
Message-ID: <CAP6exYJYC0ALa6cV7krft_5mb5_UG1NFU1UGphXrFKKXG_eM2A@mail.gmail.com> (raw)
"why is the formatting so weird" someone asked me.
I am guessing, looking at RFC 1, that it was formatted with an
ancestor of runoff but ... anyone?
ron
next reply other threads:[~2019-10-04 22:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 22:41 ron minnich [this message]
2019-10-08 13:21 ` Tony Finch
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=CAP6exYJYC0ALa6cV7krft_5mb5_UG1NFU1UGphXrFKKXG_eM2A@mail.gmail.com \
--to=rminnich@gmail.com \
--cc=tuhs@minnie.tuhs.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).