From: Julien Lepiller <julien@lepiller.eu>
To: muradm <mail@muradm.net>
Cc: 49804-done@debbugs.gnu.org, 49771-done@debbugs.gnu.org
Subject: bug#49804: [PATCH] services: pam-limits: fix limits.conf location
Date: Sat, 7 Aug 2021 17:35:47 +0200 [thread overview]
Message-ID: <20210807173547.12257ae6@tachikoma.lepiller.eu> (raw)
In-Reply-To: <874kc9n9fr.fsf@muradm.net>
Le Sun, 01 Aug 2021 06:14:00 +0300,
muradm <mail@muradm.net> a écrit :
> * gnu/services/base.scm: fix limits.conf location
>
> This fixes #49771
>
Pushed as 29883f113087edaf24570fbd7f1113df907f1099, thank you!
prev parent reply other threads:[~2021-08-07 15:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-01 3:14 [bug#49804] [PATCH] services: pam-limits: fix limits.conf location muradm
2021-08-07 15:35 ` Julien Lepiller [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=20210807173547.12257ae6@tachikoma.lepiller.eu \
--to=julien@lepiller.eu \
--cc=49771-done@debbugs.gnu.org \
--cc=49804-done@debbugs.gnu.org \
--cc=mail@muradm.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).