From: EuAndreh via Guix-patches via <guix-patches@gnu.org>
To: 58590@debbugs.gnu.org
Cc: EuAndreh <eu@euandre.org>, mail@cbaines.net
Subject: [bug#58590] [PATCH 0/2] Rework nginx-shepherd reload
Date: Mon, 17 Oct 2022 17:57:17 -0300 [thread overview]
Message-ID: <20221017205719.5704-1-eu@euandre.org> (raw)
As discussed in [0], improve the documentation of the "reload" action
of nginx, to avoid letting users get into the pitfall of thinking that
a this changes the configuration file, or enables a configuration file
change to be deployed.
[0]: https://issues.guix.gnu.org/58405
EuAndreh (2):
services: nginx: Use nginx-action over inline gexp.
services: nginx: Improve reload action documentation.
gnu/services/web.scm | 14 ++++++--------
1 file changed, 6 insertions(+), 8 deletions(-)
--
2.38.0
next reply other threads:[~2022-10-17 20:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 20:57 EuAndreh via Guix-patches via [this message]
2022-10-17 20:57 ` [bug#58590] [PATCH 1/2] services: nginx: Use nginx-action over inline gexp EuAndreh via Guix-patches via
2022-10-17 21:28 ` [bug#58594] [PATCH 2/2] services: nginx: Improve reload action documentation EuAndreh via Guix-patches via
[not found] ` <handler.58594.B.16660421334234.ack@debbugs.gnu.org>
2022-10-17 21:42 ` [bug#58594] Acknowledgement ([PATCH 2/2] services: nginx: Improve reload action documentation.) EuAndreh via Guix-patches via
2022-10-17 20:57 ` [bug#58589] [PATCH 2/2] services: nginx: Improve reload action documentation EuAndreh via Guix-patches via
[not found] ` <handler.58589.B.1666040265948.ack@debbugs.gnu.org>
2022-10-17 21:49 ` [bug#58589] Acknowledgement ([PATCH 2/2] services: nginx: Improve reload action documentation.) EuAndreh via Guix-patches via
2022-10-18 10:16 ` bug#58590: [PATCH 0/2] Rework nginx-shepherd reload Christopher Baines
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=20221017205719.5704-1-eu@euandre.org \
--to=guix-patches@gnu.org \
--cc=58590@debbugs.gnu.org \
--cc=eu@euandre.org \
--cc=mail@cbaines.net \
/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).