From: John C. Orthoefer jco@bbn.com
Subject: imminent release
Date: Fri, 31 Mar 1995 14:11:33 -0500 [thread overview]
Message-ID: <19950331191133.Qra-v5NiSXirTTW-C7G8cMOwOVFYTIdTD7Sk8T5NvZA@z> (raw)
> [about reply-to: lines]
Well there are reasons to run a list with and without a reply to line
set to the list. I've run one's set up both ways. I personly don't
care since my mailer is smart enought to pull the lines I ask for in
reply.
johno
-
John Orthoefer | Take this out and a Unix Demon will dog your steps from
<jco@bbn.com> | now until the time_t's wrap around.
617-873-6188 | -- Curse from the tunefs(8) man page source
next reply other threads:[~1995-03-31 19:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-03-31 19:11 John [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-03-31 22:19 philw
1995-03-31 19:22 Scott
1995-03-31 15:30 Rich
1995-03-31 14:07 Steve
1995-03-31 8:21 Scott
1995-03-31 8:00 philw
1995-03-31 7:01 David
1995-03-30 14:21 Steve
1995-03-30 7:02 Rich
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=19950331191133.Qra-v5NiSXirTTW-C7G8cMOwOVFYTIdTD7Sk8T5NvZA@z \
--to=9fans@9fans.net \
/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).