From: Earl Baugh <earl.baugh@gmail.com>
To: Warren Toomey <wkt@tuhs.org>
Cc: TUHS@tuhs.org
Subject: Re: [TUHS] Poll: good location for Unix documentation?
Date: Sun, 29 Sep 2019 19:02:45 -0400 [thread overview]
Message-ID: <D0F905DE-8215-4884-911B-27FA98E495AB@gmail.com> (raw)
In-Reply-To: <20190929213446.GA30379@minnie.tuhs.org>
I really would suggest first and foremost just getting stuff scanned. Archive.org does pull from bitsavers ( according to Jason when I talked to him ) so posting there should hit both. Redundancy is good. So keeping it on your site as well doesn’t hurt. And having TUHS as a place to look at to start makes a lot of sense to me.
Earl
Sent from my iPhone
> On Sep 29, 2019, at 5:35 PM, Warren Toomey <wkt@tuhs.org> wrote:
>
> On Sun, Sep 29, 2019 at 02:53:20PM -0400, Noel Chiappa wrote:
>> BitSavers seems to be the canonical location for old computer documentation.
>
> Looks like BitSavers is the recommendation. Can someone point me at the
> docs that outline the procedure to get documents to Al (others as well?) for
> consideration.
>
> I might put things in both bitsavers.org and archive.org.
>
> Cheers, Warren
next prev parent reply other threads:[~2019-09-29 23:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-29 18:53 Noel Chiappa
2019-09-29 20:11 ` Brian L. Stuart
2019-09-29 20:23 ` Clem Cole
2019-09-29 21:34 ` Warren Toomey
2019-09-29 22:40 ` Dave Horsfall
2019-09-29 23:02 ` Earl Baugh [this message]
2019-10-07 18:38 ` Al Kossow
-- strict thread matches above, loose matches on Subject: below --
2019-09-30 21:41 Noel Chiappa
2019-09-29 21:54 Noel Chiappa
2019-09-29 23:03 ` Brian L. Stuart
2019-09-30 1:13 ` Warner Losh
2019-09-28 2:02 Warren Toomey
2019-09-28 2:10 ` Warren Toomey
2019-09-28 4:56 ` Lars Brinkhoff
2019-09-28 2:38 ` Adam Thornton
2019-09-29 8:25 ` Jason Stevens
2019-09-29 8:52 ` SPC
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=D0F905DE-8215-4884-911B-27FA98E495AB@gmail.com \
--to=earl.baugh@gmail.com \
--cc=TUHS@tuhs.org \
--cc=wkt@tuhs.org \
/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).