all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 69302@debbugs.gnu.org
Subject: [bug#69302] [PATCH 1/2] doc: Add “Getting Started with the System” section.
Date: Sat, 24 Feb 2024 12:30:17 +0100	[thread overview]
Message-ID: <87frxicd6e.fsf@gnu.org> (raw)
In-Reply-To: <87v86ge2p8.fsf@pelzflorian.de> (pelzflorian@pelzflorian.de's message of "Thu, 22 Feb 2024 20:09:07 +0100")

Hi!

"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:

> This rewrite makes Guix System more approachable.  Thank you for the tip
> with “guix style -f”!

:-)

> Ludovic Courtès <ludo@gnu.org> writes:
>> * doc/guix.texi (Getting Started with the System): New node.
>> (After System Installation): Refer to it.  Remove note about ‘sudo guix
>> pull’.
>
> I was alarmed that you remove the note about sudo, but indeed you just
> moved it and not removed.
>
>> (Getting Started): Refer to it.  Remove note about ‘guix system roll-back’.
>
> As above.

Right, I’ll clarify that in the commit log.

> Could you add a reference @uref{https://git-scm.com/book/en/, Git} like
> we do in the “Invoking guix pull” section?

Sure, will do.

>> +The previous section showed the overall workflow you would follow when
>> +administrating a Guix System machine (@pxref{Getting Started with the
>
> “administering” seems more correct than “administrating”.  I’m not a
> native English speaker though.

Probably, I’m always hesitant.

>>  The operating system is configured by providing an
>>  @code{operating-system} declaration in a file that can then be passed to
>> -the @command{guix system} command (@pxref{Invoking guix system}).  A
>> -simple setup, with the default Linux-Libre
>> -kernel, initial RAM disk, and a couple of system services added to those
>> +the @command{guix system} command, as we've seen before (@pxref{Invoking
>> +guix system}).  […]
>
> Could you move the (@pxref{Invoking guix system}) before the “, as we've
> seen before”?  Otherwise it appears as if “before” refers to “Invoking
> guix system”.

I like to avoid parenthetical expressions in the middle of a sentence,
as it breaks the flow, but in this case you’re right that it makes the
text ambiguous.  I’ll change it.

Thanks!

Ludo’.




  reply	other threads:[~2024-02-24 11:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-21 14:58 [bug#69302] [PATCH 0/2] New "Getting Started" section for Guix System Ludovic Courtès
2024-02-21 16:47 ` [bug#69302] [PATCH 1/2] doc: Add “Getting Started with the System” section Ludovic Courtès
2024-02-22 15:57   ` Oleg Pykhalov
2024-02-24 11:26     ` Ludovic Courtès
2024-02-24 22:24       ` Oleg Pykhalov
2024-02-24 22:35         ` Ludovic Courtès
2024-02-25 14:48           ` [bug#69302] [PATCH v2 0/2] New "Getting Started" section for Guix System Ludovic Courtès
2024-02-25 14:48           ` [bug#69302] [PATCH v2 1/2] doc: Add “Getting Started with the System” section Ludovic Courtès
2024-02-27 11:21             ` pelzflorian (Florian Pelz)
2024-02-27 11:39               ` pelzflorian (Florian Pelz)
2024-02-28 21:48               ` Ludovic Courtès
2024-03-01  9:18                 ` pelzflorian (Florian Pelz)
2024-03-02 16:28                   ` bug#69302: " Ludovic Courtès
2024-02-25 14:48           ` [bug#69302] [PATCH v2 2/2] doc: Add “Inspecting Services” section Ludovic Courtès
2024-02-27 11:54             ` pelzflorian (Florian Pelz)
2024-02-22 19:09   ` [bug#69302] [PATCH 1/2] doc: Add “Getting Started with the System” section pelzflorian (Florian Pelz)
2024-02-24 11:30     ` Ludovic Courtès [this message]
2024-02-21 16:47 ` [bug#69302] [PATCH 2/2] doc: Add “Inspecting Services” section Ludovic Courtès
2024-02-22 17:56   ` pelzflorian (Florian Pelz)

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=87frxicd6e.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=69302@debbugs.gnu.org \
    --cc=pelzflorian@pelzflorian.de \
    /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.