From: Andrew Tropin <andrew@trop.in>
To: Felix Lechner <felix.lechner@lease-up.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: An apology
Date: Fri, 14 Oct 2022 09:42:11 +0400 [thread overview]
Message-ID: <87tu47arm4.fsf@trop.in> (raw)
In-Reply-To: <CAFHYt55iijh1Nu7EtrbBJeh081_a26Dbcda+NsHJj52PbW0d0Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2126 bytes --]
On 2022-10-13 09:36, Felix Lechner wrote:
> Hi Andrew,
>
> Please accept my apologies for sending the message below. Aside from
> being impolite, my note was also ill-timed given your newly-won status
> as a committer. I could have hardly been more tone-deaf. If at all, I
> should have written in private.
>
> While not a great explanation, I occasionally spend time with
> scientists and engineers working on weapons. Over the years, I have
> become cynical about the progress of technology. It was not the first
> time that I have been vocal in technical forums about embracing life
> rather than taking it.
>
> I felt sorry for several weeks and hope you can forgive me. May this
> follow-up in public remove any stain from
> your good name.
No worries, I'm not offended or anything :) I just have a huge email
backlog and didn't allocate the time to reply yet, sorry. Also, have an
additional time wastes due to unfortunate events happening in my country
and for now I usually read, mark as todo and skip messages, which
don't block anyone.
>
> Thanks for Guix Home!
My pleasure!)
>
> Sincerely,
> Felix
>
>
> ---------- Forwarded message ---------
> From: Felix Lechner <felix.lechner@lease-up.com>
> Date: Thu, Aug 11, 2022 at 8:09 AM
> Subject: Re: [POSTMORTEM] Subkey is not authorized by .guix-authorizations
> To: Guix Devel <guix-devel@gnu.org>
>
>
> Hi,
>
> On Thu, Aug 11, 2022 at 7:27 AM Andrew Tropin <andrew@trop.in> wrote:
>>
>> Re: [POSTMORTEM]
>
> I have likewise used those words to describe concluding reports or to
> communicate lessons learned, but upon reflection I now prefer
> "incident summary" or "debrief". [1] Since both of my suggested
> replacements are associated with the military, they are also not great
> examples of favoring life over death, but at least the parties are not
> yet in the morgue, so there is hope.
>
> Long live Guix!
>
> Kind regards
> Felix Lechner
>
> [1] "debriefing strategies maximize ... the collective experience",
> https://en.wikipedia.org/wiki/Debriefing
--
Best regards,
Andrew Tropin
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2022-10-14 5:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 16:36 An apology Felix Lechner via Development of GNU Guix and the GNU System distribution.
2022-10-14 5:42 ` Andrew Tropin [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tu47arm4.fsf@trop.in \
--to=andrew@trop.in \
--cc=felix.lechner@lease-up.com \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).