The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Will Senn <will.senn@gmail.com>
To: Warner Losh <imp@bsdimp.com>, segaloco <segaloco@protonmail.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>,
	The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Documents for UNIX Collections
Date: Tue, 9 Aug 2022 12:22:57 -0500	[thread overview]
Message-ID: <d03624bc-fbdf-3421-2ede-2e44c3a369ed@gmail.com> (raw)
In-Reply-To: <CANCZdfqm0V0cxz_qRkY0HAz2zh_GZZJFDpeE8=YfGwXRv=HCEg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2026 bytes --]

Amen to that. Scanning is very difficult to get right and folks that get 
it working well aren't great about making simplified processes 
accessible to others.

Will

On 8/9/22 12:16 PM, Warner Losh wrote:
> Perhaps Al could offer those areas that segaloco could use to 
> improve the scans.
>
> Let's get over the 'presentation' of the issue (which we all are 
> thinking in the back of our minds sucked) and understand how we call 
> can produce better scans without getting overly defensive or 
> protective about it (both reactions don't really help, and frankly 
> aren't fun to read played out in a public list).
>
> Warner
>
> On Tue, Aug 9, 2022 at 9:15 AM segaloco via TUHS <tuhs@tuhs.org> wrote:
>
>     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
>

[-- Attachment #2: Type: text/html, Size: 3482 bytes --]

  reply	other threads:[~2022-08-09 17:24 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
2022-08-09 17:16         ` Warner Losh
2022-08-09 17:22           ` Will Senn [this message]
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=d03624bc-fbdf-3421-2ede-2e44c3a369ed@gmail.com \
    --to=will.senn@gmail.com \
    --cc=imp@bsdimp.com \
    --cc=segaloco@protonmail.com \
    --cc=tuhs@minnie.tuhs.org \
    --cc=tuhs@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).