9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Scott Schwartz <schwartz@bio.cse.psu.edu>
To: "Boyd Roberts" <boyd@planete.net>
Cc: 9fans@cs.psu.edu
Subject: Re: [9fans] list
Date: Wed, 10 Jan 2001 12:49:24 -0500	[thread overview]
Message-ID: <20010110174924.20999.qmail@g.bio.cse.psu.edu> (raw)
In-Reply-To: Message from "Boyd Roberts" <boyd@planete.net>  of "Wed, 10 Jan 2001 18:21:33 +0100." <00e101c07b29$c7c00660$0ab9c6d4@cybercable.fr>

| looks like it's missing a:
|     Reply-To: 9fans@cse.psu.edu
| seems to have started today.

It turns out that the mailing list software that's been foisted on us
has a bug, wherein the Reply-To-list feature messes up the From lines
in the archived messages;  I turned it off to test the story.   So,
now, can we live with the workaround?



  reply	other threads:[~2001-01-10 17:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-10 17:21 Boyd Roberts
2001-01-10 17:49 ` Scott Schwartz [this message]
2001-01-11  2:14 okamoto
2001-01-11  9:36 ` Boyd Roberts

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=20010110174924.20999.qmail@g.bio.cse.psu.edu \
    --to=schwartz@bio.cse.psu.edu \
    --cc=9fans@cs.psu.edu \
    --cc=boyd@planete.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).