From: krewat@kilonet.net (Arthur Krewat)
Subject: [TUHS] Any BSDi interest?
Date: Sun, 19 Feb 2017 19:09:14 -0500 [thread overview]
Message-ID: <8df70e17-f615-871e-7a70-6118287a0ede@kilonet.net> (raw)
In-Reply-To: <1487543997.751282.886126728.48CE1043@webmail.messagingengine.com>
If you don't archive it, you're a luser.
:)
On 2/19/2017 5:39 PM, Cory Smelosky wrote:
> Hi,
>
> Forgot I'm sitting on a lot of BSDi sources/binaries.
>
> Is there any interest in this aside from me? ;)
>
next prev parent reply other threads:[~2017-02-20 0:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-19 22:39 Cory Smelosky
2017-02-20 0:09 ` Arthur Krewat [this message]
2017-02-20 1:31 ` Cory Smelosky
2017-02-20 3:59 ` Wesley Parish
2017-02-20 4:31 ` Jason Stevens
2017-02-22 23:21 ` Dave Horsfall
2017-02-23 0:10 ` Cory Smelosky
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=8df70e17-f615-871e-7a70-6118287a0ede@kilonet.net \
--to=krewat@kilonet.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).