unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Felix Lechner via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: Guix Devel <guix-devel@gnu.org>
Subject: Re: [POSTMORTEM] Subkey is not authorized by .guix-authorizations
Date: Thu, 11 Aug 2022 08:09:10 -0700	[thread overview]
Message-ID: <CAFHYt57=fDCVYPZXnS7k2OgLi6xb5-t154jhL4Pii3iV6wE=Qw@mail.gmail.com> (raw)
In-Reply-To: <87tu6idfgd.fsf@trop.in>

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


  reply	other threads:[~2022-08-11 15:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-11 14:26 [POSTMORTEM] Subkey is not authorized by .guix-authorizations Andrew Tropin
2022-08-11 15:09 ` Felix Lechner via Development of GNU Guix and the GNU System distribution. [this message]
2022-08-11 15:11 ` Maxime Devos
2022-08-11 15:25   ` John Kehayias
2022-09-02 13:23 ` Ludovic Courtès
2022-09-05  7:07   ` Andrew Tropin
2022-09-05  9:53     ` Ludovic Courtès
2022-09-05 11:50       ` Tobias Geerinckx-Rice

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='CAFHYt57=fDCVYPZXnS7k2OgLi6xb5-t154jhL4Pii3iV6wE=Qw@mail.gmail.com' \
    --to=guix-devel@gnu.org \
    --cc=felix.lechner@lease-up.com \
    /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).