From: aki@insinga.com
To: tuhs@tuhs.org
Subject: [TUHS] Re: Sad but not unexpected news about the LCM-L
Date: Wed, 26 Jun 2024 11:56:12 -0500 [thread overview]
Message-ID: <d03d4307514a23031e4591c831f58070@insinga.com> (raw)
In-Reply-To: <7wikxwb6zl.fsf@junk.nocrew.org>
It's not like this was the first time he faced cancer. It's too bad he
didn't take the lesson from an earlier encounter and do this decades
ago. Now if only his family would take those wishes of his into account
and tell the lawyers to finish the job.
On 2024-06-26 00:36, Lars Brinkhoff wrote:
> Dan Cross wrote:
>> Allen was a man dying of cancer. LCM+L was important to him, but he
>> neglected to leave explicit instructions to set up an endowment for
>> it; that's unfortunate, but it was an oversight: he had other
>> concerns.
>
> The oversight would be that it was done too late. Such paperwork was
> in
> progress, but it was not completed before his death.
next prev parent reply other threads:[~2024-06-26 16:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 18:17 [TUHS] " Clem Cole
2024-06-26 0:56 ` [TUHS] " Aron Insinga
2024-06-26 1:29 ` Larry McVoy
2024-06-26 3:34 ` [TUHS] Re: Trust stuff, " John Levine
2024-06-26 9:22 ` [TUHS] Wills. (Was: Sad but not unexpected news about the LCM-L) Ralph Corderoy
2024-06-26 1:42 ` [TUHS] Re: Sad but not unexpected news about the LCM-L George Michaelson
2024-06-26 17:22 ` aki
2024-06-26 1:44 ` Paul Guertin
2024-06-26 1:46 ` Dan Cross
2024-06-26 2:46 ` Paul Guertin
2024-06-26 5:36 ` Lars Brinkhoff
2024-06-26 14:30 ` [TUHS] Planning for the future was " Will Senn
2024-06-26 15:18 ` [TUHS] " Al Kossow
2024-06-26 21:57 ` [TUHS] Re: Planning for the future Warren Toomey via TUHS
2024-06-30 13:05 ` Will Senn
2024-06-26 16:56 ` aki [this message]
2024-06-25 18:45 [TUHS] Re: Sad but not unexpected news about the LCM-L Noel Chiappa
2024-06-25 18:53 ` Al Kossow
2024-06-27 15:19 Noel Chiappa
2024-06-27 17:06 ` Al Kossow
2024-06-27 17:32 ` John Levine
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=d03d4307514a23031e4591c831f58070@insinga.com \
--to=aki@insinga.com \
--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).