From: zimoun <zimon.toutoune@gmail.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: 24097@debbugs.gnu.org
Subject: bug#24097: ‘operating-system’ lacks a way to populate /run/modprobe.d
Date: Fri, 18 Dec 2020 20:43:54 +0100 [thread overview]
Message-ID: <861rfmx5l1.fsf@gmail.com> (raw)
In-Reply-To: <87lh0lg4xu.fsf@gnu.org> ("Ludovic Courtès"'s message of "Thu, 28 Jul 2016 17:25:49 +0200")
Hi Ludo,
On Thu, 28 Jul 2016 at 17:25, ludo@gnu.org (Ludovic Courtès) wrote:
> See the example at:
>
> https://lists.gnu.org/archive/html/help-guix/2016-07/msg00231.html
It seems a wishlist. Well, I do not know if it is still relevant 4
years later. If yes, how to make it happen?
All the best,
simon
next prev parent reply other threads:[~2020-12-18 19:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 15:25 bug#24097: ‘operating-system’ lacks a way to populate /run/modprobe.d Ludovic Courtès
2020-12-18 19:43 ` zimoun [this message]
2021-01-11 13:04 ` zimoun
2021-01-14 11:07 ` Ludovic Courtès
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=861rfmx5l1.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=24097@debbugs.gnu.org \
--cc=ludo@gnu.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).