unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Xinglu Chen <public@yoctocell.xyz>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
	"Attila Lendvai" <attila@lendvai.name>,
	52600@debbugs.gnu.org, "Andrew Tropin" <andrew@trop.in>
Subject: [bug#52600] [PATCH] doc: Document (gnu services configuration).
Date: Thu, 06 Jan 2022 09:20:38 -0500	[thread overview]
Message-ID: <87y23tq72h.fsf@gmail.com> (raw)
In-Reply-To: <87ilvfd2lx.fsf@yoctocell.xyz> (Xinglu Chen's message of "Thu, 23 Dec 2021 11:42:18 +0100")

Hi Xinglu,

Sorry for jumping in late.

Xinglu Chen <public@yoctocell.xyz> writes:

>> As for ‘define-configuration’ vs. (guix records) vs. SRFI-9…  I don’t
>> think we really discussed the issue or agreed on something.

[...]

> Agreed, since ‘define-configuration’ & friends are now documented, it
> makes even more sense to use them.
>
>> Thanks for substantially improving the manual!

I haven't reviewed the feasibility yet, but since Guix records now have
"sanitizers" that can be used to validate the field values, I have been
wondering if these could be used in define-configuration.

Anyway, thanks a lot for improving and documenting
'define-configuration' :-).

Maxim






      parent reply	other threads:[~2022-01-06 14:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-18 15:12 [bug#52600] [PATCH] doc: Document (gnu services configuration) Xinglu Chen
2021-12-22 22:14 ` Ludovic Courtès
2021-12-23 10:42   ` Xinglu Chen
     [not found]     ` <IxmgfjO9lp2ladC6D9lHKww0c_r1R0JsnoPJbKD9vg1StRq5QIaZyf3If6Jc16dYnqBdbM0VAjy2PDpZBWxwhHHvgJj_lL8sE4SJ8AsG3po=@lendvai.name>
2021-12-23 12:54       ` Xinglu Chen
2021-12-23 15:21         ` Attila Lendvai
2022-01-18  9:24         ` Attila Lendvai
2022-01-06 14:20     ` Maxim Cournoyer [this message]

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=87y23tq72h.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=52600@debbugs.gnu.org \
    --cc=andrew@trop.in \
    --cc=attila@lendvai.name \
    --cc=ludo@gnu.org \
    --cc=public@yoctocell.xyz \
    /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).