unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Grant Shoshin Shangreaux <grant@churls.world>
Cc: guix-devel@gnu.org
Subject: Re: PATCH: clarify some of the Guix Linode recipe
Date: Wed, 08 Sep 2021 22:37:25 +0200	[thread overview]
Message-ID: <87ee9y248q.fsf@gnu.org> (raw)
In-Reply-To: <85wnobt2nw.fsf@churls.world> (Grant Shoshin Shangreaux's message of "Tue, 24 Aug 2021 07:59:49 -0500")

Hi Grant,

Grant Shoshin Shangreaux <grant@churls.world> skribis:

> Hello! I hope I'm not double posting, but I think the email I intended
> to send before never made it out of my outbox. I recently set up GuixSD
> on Linode following the cookbook. I hit a few snags along the way where
> I either missed something or misunderstood, so I thought I'd offer a
> patch with a few clarifications to the article. Some of it is likely due
> to changes in the Linode UI. Hopefully this patch is helpful.

Looks like this message fell through the summer cracks…

> From 446bf79c3733936306e9fd95c46cbfd495f6bc2a Mon Sep 17 00:00:00 2001
> From: Grant Shangreaux <grant@unabridgedsoftware.com>
> Date: Mon, 23 Aug 2021 22:47:05 -0500
> Subject: [PATCH] doc: add clarifications to Linode cookbook recipe
>
> * doc/guix-cookbook.texi: clarify Linode recipe
>
> Reword paragraph about adding the Guix device disk to Debian config.
> Improve example commands for sftp-ing files to the server.
> Minor wording fixes

This looks like a welcome improvement, so I went ahead and applied it.
(Cc’ing Joshua, who originally wrote this section.)

Thanks!

Ludo’.


  reply	other threads:[~2021-09-08 20:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-24 12:59 PATCH: clarify some of the Guix Linode recipe Grant Shoshin Shangreaux
2021-09-08 20:37 ` Ludovic Courtès [this message]
2021-09-09 18:26 ` jbranso

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=87ee9y248q.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=grant@churls.world \
    --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).