From: rudi.j.blom at gmail.com (Rudi Blom)
Subject: [COFF] [TUHS] Happy birthday, Morris Worm!
Date: Sun, 3 Nov 2019 14:05:28 +0700 [thread overview]
Message-ID: <CAMYpm85FNiLLF=J1-KSo5o2rdONz9r+zO1Jmy93DE0nfrqmEQg@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2N3HDnQSTv6x2sr-0rn8vUaLNMaRNSi5wc5u+VRPeO=Fw@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1062 bytes --]
+1
Maybe I was a bit negative but then I did mention WINDOWS System Updating.
Anyone here who studied there by the way?
Have fun.
On 03/11/2019, Clem Cole <clemc at ccc.com> wrote:
> Oh I think we have learned. We still have a WSU’s to go
>
> On Sat, Nov 2, 2019 at 7:05 PM Rudi Blom <rudi.j.blom at gmail.com> wrote:
>
>> >From: Clem Cole <clemc at ccc.com>
>> >To: Dan Cross <crossd at gmail.com>
>> >Cc: Computer Old Farts Followers <coff at tuhs.org>, Dave Horsfall <
>> dave at horsfall.org>, >The Eunuchs Hysterical Society <tuhs at tuhs.org>
>> >Bcc:
>> >Date: Fri, 1 Nov 2019 14:55:19 -0700
>> >Subject: Re: [COFF] [TUHS] Happy birthday, Morris Worm!
>> >+1. Well said Dan.
>> >
>> >We all have made and will make mistakes in the future. It was an error
>> and we all learned >from it. It’s not helpful to continue to hark back
>> on
>> it.
>>
>> Of course after having had my monthly Windows update session I really
>> wonder if we learned from it.
>>
>> Cheers,
>> uncle rubl
>>
> --
> Sent from a handheld expect more typos than usual
>
next prev parent reply other threads:[~2019-11-03 7:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-03 2:05 rudi.j.blom
2019-11-03 4:21 ` clemc
2019-11-03 7:05 ` rudi.j.blom [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-11-01 20:36 [COFF] " dave
2019-11-01 21:12 ` [COFF] [TUHS] " crossd
2019-11-01 21:55 ` clemc
2019-11-01 22:25 ` a.phillip.garcia
2019-11-01 21:49 ` a.phillip.garcia
2019-11-02 6:35 ` wlc
2019-11-02 6:44 ` wlc
2019-11-02 7:31 ` a.phillip.garcia
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='CAMYpm85FNiLLF=J1-KSo5o2rdONz9r+zO1Jmy93DE0nfrqmEQg@mail.gmail.com' \
--to=coff@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).