unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Dariqq <dariqq@posteo.net>
Cc: Tanguy Le Carrour <tanguy@bioneland.org>,
	Maxim Cournoyer <maxim.cournoyer@gmail.com>,
	paren@disroot.org, Florian Pelz <pelzflorian@pelzflorian.de>,
	Andrew Tropin <andrew@trop.in>,
	73383-done@debbugs.gnu.org
Subject: bug#73383: [PATCH v2 0/2] home-shepherd-configuration: add silent? and document daemonize?
Date: Mon, 14 Oct 2024 13:07:00 +0200	[thread overview]
Message-ID: <87iktv3puz.fsf@gnu.org> (raw)
In-Reply-To: <cover.1728634996.git.dariqq@posteo.net> (dariqq@posteo.net's message of "Fri, 11 Oct 2024 08:39:07 +0000")

Hello,

Dariqq <dariqq@posteo.net> skribis:

> Here is v2:
>
> Changes:
>  * Change default-value of the silent? field to #t.
>  * Update the documentation. I added something that (hopefully) makes it obvious that the field is intended to be used together with the auto-start? field.
>  * Added a second patch to document the daemonize? field and export the field-accessor. Should it warn about the issue when dameonize? is #f but auto-start? is #t blocking logins?
>
> Dariqq (2):
>   home: home-shepherd-configuration: Add silent? field.
>   doc: Document home-shepherd-configuration-daemonize?

Applied, thanks!

Ludo’.




      parent reply	other threads:[~2024-10-14 11:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-20 12:39 [bug#73383] [PATCH] home: home-shepherd-configuration: Add silent? field Dariqq
2024-09-25 15:57 ` Ludovic Courtès
2024-09-27 14:06   ` Dariqq
2024-10-11  8:39 ` [bug#73383] [PATCH v2 0/2] home-shepherd-configuration: add silent? and document daemonize? Dariqq
2024-10-11  8:39   ` [bug#73383] [PATCH v2 1/2] home: home-shepherd-configuration: Add silent? field Dariqq
2024-10-11  8:39   ` [bug#73383] [PATCH v2 2/2] doc: Document home-shepherd-configuration-daemonize? Dariqq
2024-10-14 11:07   ` Ludovic Courtès [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=87iktv3puz.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=73383-done@debbugs.gnu.org \
    --cc=andrew@trop.in \
    --cc=dariqq@posteo.net \
    --cc=maxim.cournoyer@gmail.com \
    --cc=paren@disroot.org \
    --cc=pelzflorian@pelzflorian.de \
    --cc=tanguy@bioneland.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).