all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Maxim Cournoyer <maxim.cournoyer@gmail.com>,
	Matthew Trzcinski <matt@excalamus.com>,
	72439@debbugs.gnu.org
Subject: [bug#72439] [PATCH] doc: Setting Up the Daemon: Add paragraphs whom this section is for.
Date: Fri, 16 Aug 2024 20:42:49 +0200	[thread overview]
Message-ID: <878qwwb97a.fsf@pelzflorian.de> (raw)
In-Reply-To: <8734n4788z.fsf@gnu.org> ("Ludovic Courtès"'s message of "Fri, 16 Aug 2024 18:17:00 +0200")

Hi Ludo.  Ohh sorry, I pushed this already when it had one review and a
week was over.

Ludovic Courtès <ludo@gnu.org> writes:
> Florian Pelz <pelzflorian@pelzflorian.de> skribis:
>
>> * doc/guix.texi (Setting Up the Daemon): Specify intended audience.
>>
>> Change-Id: I784c5f720aa87bddb6455e42181a1e9de5d7ec9a
>
> Good idea.
>
>> +During the installation, the @dfn{build daemon} that must be running
>
> s/the// (I think?)

IMHO a definite article is warranted, because the installation was
described in the previous section.


>> +However, some of us have reason to replace outdated daemon versions,
>> +tweak it, perform builds on other machines (@pxref{Daemon Offload
>> +Setup}) or start it manually in special environments like Chroots
>
> I’d add a comma before “or”,

An Oxford comma is often used and sometimes not in the manual.

Such as

> 22.6 Alternative Setups
> =======================
> 
> Alternative setups than Emacs may let you work on Guix with a similar
> development experience and they might work better with the tools you
> currently use or help you make the transition to Emacs.

or

> 22.8.6 Cyclic Module Dependencies
> ---------------------------------
> […]
>    Care would need to be taken to ensure the above procedure is only
> ever used in a package delayed fields or within another procedure also
> not called at the top level.

We could enforce one unified style, it just is less natural to me.


> and s/Chroots/``chroots''/
>
> Otherwise LGTM, thanks!
>
> Ludo’.


Yes, I will prepare a follow-up patch for chroots.

Regards,
Florian




  reply	other threads:[~2024-08-16 18:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-03  8:15 [bug#72439] [PATCH] doc: Setting Up the Daemon: Add paragraphs whom this section is for Florian Pelz
2024-08-05 11:41 ` [bug#72439] [PATCH v2] doc: Setting Up the Daemon: Give guidance to whom this section is useful Florian Pelz
2024-08-06  6:46 ` [bug#72439] [PATCH v3] " Florian Pelz
2024-08-08  9:16 ` [bug#72439] [PATCH] doc: Setting Up the Daemon: Add paragraphs whom this section is for Vincent Legoll
2024-08-08 11:22   ` pelzflorian (Florian Pelz)
2024-08-09  9:09 ` [bug#72439] [PATCH v4] doc: Setting Up the Daemon: Give guidance to whom this section is useful Florian Pelz
2024-08-09 13:23   ` Vincent Legoll
2024-08-10 14:11     ` bug#72439: " pelzflorian (Florian Pelz)
2024-08-16 16:17 ` [bug#72439] [PATCH] doc: Setting Up the Daemon: Add paragraphs whom this section is for Ludovic Courtès
2024-08-16 18:42   ` pelzflorian (Florian Pelz) [this message]
2024-08-16 21:05   ` 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=878qwwb97a.fsf@pelzflorian.de \
    --to=pelzflorian@pelzflorian.de \
    --cc=72439@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=matt@excalamus.com \
    --cc=maxim.cournoyer@gmail.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.