The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: segaloco via TUHS <tuhs@tuhs.org>
To: Al Kossow <aek@bitsavers.org>
Cc: TUHS main list <tuhs@minnie.tuhs.org>, tuhs@tuhs.org
Subject: [TUHS] Re: Documents for UNIX Collections
Date: Tue, 09 Aug 2022 15:14:57 +0000	[thread overview]
Message-ID: <fHmPLPUpMGQ1lG5qfgxKjtR2wr8D398KJqkJ5nYIJVcK1MqzK5YD2HJYJZs7rJuRoMb6Ox4sLmjubyuu7d50Hz-jiG92qTHR1jqi6HbOXU0=@protonmail.com> (raw)
In-Reply-To: <dbfa97ad-f1e3-d5cf-9945-9c7534980436@bitsavers.org>

I'm literally the one doing it now.  Got a problem with it?  Tough, you're not the one doing *these* documents.  Literally nobody is asking you to take on the magnanimous task of "cleaning them up".  Do it yourself or step aside, but again, don't derail a thread about work I am going to do to lob criticism of work you aren't going to do.  Be childish somewhere else.  Sorry Al is stinking up this thread, this is the last thing I wanted, I'm just contributing.

- Matt G.

------- Original Message -------
On Tuesday, August 9th, 2022 at 5:49 AM, Al Kossow <aek@bitsavers.org> wrote:


> On 8/9/22 12:00 AM, segaloco wrote:
>
> > Frankly I will scan however I want given I am both paying for the documents myself and scanning them in my own free time.
>
>
> Queue the virtue signaling.
>
> That is EXACTLY why I sent the rude message.
> I spent days cleaning up your scans to meet the bitsavers scanning quality requirements of the
> garbage you produced, because you spent a WHOLE DAY scanning them.
>
> I've been doing this for twenty years, don't talk to me about time or money spent doing this

  reply	other threads:[~2022-08-09 15:15 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
2022-08-09 12:49     ` Al Kossow
2022-08-09 15:14       ` segaloco via TUHS [this message]
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='fHmPLPUpMGQ1lG5qfgxKjtR2wr8D398KJqkJ5nYIJVcK1MqzK5YD2HJYJZs7rJuRoMb6Ox4sLmjubyuu7d50Hz-jiG92qTHR1jqi6HbOXU0=@protonmail.com' \
    --to=tuhs@tuhs.org \
    --cc=aek@bitsavers.org \
    --cc=segaloco@protonmail.com \
    --cc=tuhs@minnie.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).