9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: David Gordon Hogan <dhog@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: 9fans -- confirmation of subscription -- request 349718
Date: Thu,  2 Nov 2000 14:18:58 -0500	[thread overview]
Message-ID: <20001102191859.E9ECC199F1@mail> (raw)

[-- Attachment #1: Type: text/plain, Size: 30 bytes --]

confirm 3.141592653559....


[-- Attachment #2: Type: message/rfc822, Size: 1598 bytes --]

From: sanfranmike@att.net
To: 9fans@cse.psu.edu
Subject: [9fans] Re: 9fans -- confirmation of subscription -- request 349718
Date: Thu, 02 Nov 2000 07:35:56 +0000
Message-ID: <20001102073556.WSCC4818.mtiwmhc21.worldnet.att.net@webmail.worldnet.att.net>

confirm 349718

             reply	other threads:[~2000-11-02 19:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-02 19:18 David Gordon Hogan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-11-02  7:35 sanfranmike
2000-11-02  7:33 sanfranmike

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=20001102191859.E9ECC199F1@mail \
    --to=dhog@plan9.bell-labs.com \
    --cc=9fans@cse.psu.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).