From: "Ludovic Courtès" <ludo@gnu.org>
To: John Kehayias <john.kehayias@protonmail.com>
Cc: 60112@debbugs.gnu.org
Subject: [bug#60112] [PATCH] website: Add post about guix shell fhs option.
Date: Wed, 04 Jan 2023 11:31:22 +0100 [thread overview]
Message-ID: <87mt6y616t.fsf_-_@gnu.org> (raw)
In-Reply-To: <87fscrb4ks.fsf@protonmail.com> (John Kehayias's message of "Tue, 03 Jan 2023 23:07:03 +0000")
Hi!
John Kehayias <john.kehayias@protonmail.com> skribis:
> Yes, I think now will be a good time. Sorry I didn't get to this earlier (some unfortunate urgent situations), but I did make most of the changes already. I think just the footnotes, or rewriting them into the text, is all that's left.
Cool!
> Is there anything else I should add, like other images or screen recordings? I think I'll quickly test and add the Tor browser example mentioned on the mailing list at least.
The Tor Browser example would be nice. No other suggestions from me!
Thanks,
Ludo’.
next prev parent reply other threads:[~2023-01-04 10:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 7:27 [bug#60112] [PATCH] website: Add post about guix shell fhs option John Kehayias via Guix-patches via
2022-12-25 23:58 ` Ludovic Courtès
2023-01-03 22:54 ` Ludovic Courtès
2023-01-03 23:07 ` John Kehayias via Guix-patches via
2023-01-04 10:31 ` Ludovic Courtès [this message]
2023-01-04 17:43 ` [bug#60112] [PATCH v2] " John Kehayias via Guix-patches via
2023-01-04 18:23 ` [bug#60112] [PATCH v3] " John Kehayias via Guix-patches via
2023-01-06 12:49 ` [bug#60112] [PATCH] " Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2022-12-16 23:39 Drafting a Guix blog post on the FHS container Jim Newsome
2023-01-04 17:47 ` John Kehayias
2023-01-04 18:18 ` [bug#60112] " jman via Guix-patches via
2023-01-05 21:00 ` [bug#60112] [PATCH] website: Add post about guix shell fhs option Ludovic Courtès
2023-01-05 21:03 ` John Kehayias via Guix-patches via
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=87mt6y616t.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=60112@debbugs.gnu.org \
--cc=john.kehayias@protonmail.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.