From: David Hogan dhog@plan9.cs.su.oz.au
Subject: imminent release
Date: Fri, 31 Mar 1995 02:01:01 -0500 [thread overview]
Message-ID: <19950331070101.EQem_trChiF4igPiVrWaS3rBY7CUV9L3M1UpO2OGGDk@z> (raw)
Steve Kotsopoulos <steve@ecf.toronto.edu> writes:
>Rich Salz <rsalz@osf.org> wrote:
>> I hope "the plan 9 guys" will reject anyone who replies to the
>> list rather then the sender.
>
>I hope not. The message from Rob had a 'Reply-To: 9fans@cse.psu.edu',
>probably inserted by the list software.
Which is a bad thing for the list software to do. Not adding the
Reply-To is better, because it gives the person replying the choice
of just replying to the author, or doing a group reply which will
go to the list. Can this be changed, to forestall future debacles?
next reply other threads:[~1995-03-31 7:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-03-31 7:01 David [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 19:11 John
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-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=19950331070101.EQem_trChiF4igPiVrWaS3rBY7CUV9L3M1UpO2OGGDk@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).