From: clemc@ccc.com (Clem cole)
Subject: [TUHS] DR11-W - anyone need one?
Date: Wed, 5 Jul 2017 19:12:44 -0400 [thread overview]
Message-ID: <D0BDB9CF-91E4-4BDD-8D20-468BE0053C1E@ccc.com> (raw)
In-Reply-To: <20170705225617.62ECA18C0C7@mercury.lcs.mit.edu>
Ditto. It would be handy to have in my kit but I have not immediate need
Sent from my PDP-7 Running UNIX V0 expect things to be almost but not quite.
On Jul 5, 2017, at 6:56 PM, Noel Chiappa <jnc at mercury.lcs.mit.edu> wrote:
>> From: Toby Thain
>
>> Are we to infer that neither Noel and Clem are "good homes"?
>
> Well, I said something like 'I don't have an immediate need for it, but I'd
> be happy to take it', so I guess the question is 'does someone have an
> actual, immediate use for it' (which I don't)?
>
> Noel
next prev parent reply other threads:[~2017-07-05 23:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 22:56 Noel Chiappa
2017-07-05 23:12 ` Clem cole [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-07-05 11:34 Arthur Krewat
2017-07-05 22:11 ` Arthur Krewat
2017-07-05 22:44 ` Toby Thain
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=D0BDB9CF-91E4-4BDD-8D20-468BE0053C1E@ccc.com \
--to=clemc@ccc.com \
/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).