From: segaloco via TUHS <tuhs@tuhs.org>
To: Al Kossow <aek@bitsavers.org>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Documents for UNIX Collections
Date: Tue, 09 Aug 2022 07:00:31 +0000 [thread overview]
Message-ID: <oIB9UL0QUySCn7au_OmBszebxUOlWL8N2EG8g4f5fHJbTLSaD2B-hWm458opeK7mqe0_LIU1rdrWt31NOzERbWcaWHGhIOyVs7fjixaoxUA=@protonmail.com> (raw)
In-Reply-To: <fb99975e-1428-6fa8-3d6f-5a80c27678bd@bitsavers.org>
Frankly I will scan however I want given I am both paying for the documents myself and scanning them in my own free time. You can take your elitism elsewhere rather than offering unsolicited criticism of work you aren't even going to do.
Please keep this thread on topic, contribute or don't.
- Matt G.
------- Original Message -------
On Monday, August 8th, 2022 at 5:37 PM, Al Kossow <aek@bitsavers.org> wrote:
> On 8/8/22 4:52 PM, segaloco via TUHS wrote:
>
> > I didn't expect to have more documents to share this soon, but I've just secured a trove of early System V/5.0 documents
>
>
> Hopefully, you've learned something about scanning and won't produce the same shit scans you dumped on IA
next prev parent reply other threads:[~2022-08-09 7:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 23:52 segaloco via TUHS
2022-08-09 0:37 ` Al Kossow
2022-08-09 7:00 ` segaloco via TUHS [this message]
2022-08-09 12:49 ` Al Kossow
2022-08-09 15:14 ` segaloco via TUHS
2022-08-09 17:16 ` Warner Losh
2022-08-09 17:22 ` Will Senn
2022-08-12 1:33 segaloco via TUHS
2022-08-12 2:06 ` G. Branden Robinson
2022-08-12 6:41 ` arnold
2022-08-12 11:01 Paul Ruizendaal via TUHS
2022-08-12 11:15 ` arnold
2022-08-12 11:41 ` Jonathan Gray
2022-08-12 16:06 ` Warner Losh
2022-08-12 16:37 ` Warner Losh
2022-08-13 19:51 ` Paul Ruizendaal via TUHS
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='oIB9UL0QUySCn7au_OmBszebxUOlWL8N2EG8g4f5fHJbTLSaD2B-hWm458opeK7mqe0_LIU1rdrWt31NOzERbWcaWHGhIOyVs7fjixaoxUA=@protonmail.com' \
--to=tuhs@tuhs.org \
--cc=aek@bitsavers.org \
--cc=segaloco@protonmail.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).