Github messages for voidlinux
 help / color / mirror / Atom feed
From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: dracut: move network-legacy into dracut-network package
Date: Tue, 17 Jan 2023 14:08:54 +0100	[thread overview]
Message-ID: <20230117130854.XIy_GE7dGbq_tggbXclFez0_DGvOEX5x_qhsyPuD5OQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41031@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 606 bytes --]

There's a merged pull request on the void-packages repository

dracut: move network-legacy into dracut-network package
https://github.com/void-linux/void-packages/pull/41031

Description:
Other changes:
 - remove more systemd dependent modules
 - network-manager module depends on the dbus dracut module, which in turn depends on the systemd dracut module

#### Testing the changes
- I tested the changes in this PR: **NO**

In case it helps to test and review - alpine dracut package has some similar changes - https://gitlab.alpinelinux.org/alpine/aports/-/blob/master/testing/dracut/APKBUILD#L34

      parent reply	other threads:[~2023-01-17 13:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-12  5:24 [PR PATCH] " LaszloGombos
2022-12-13  3:48 ` LaszloGombos
2022-12-13  3:55 ` ahesford
2022-12-13 18:44 ` [PR REVIEW] " paper42
2022-12-13 20:10 ` [PR PATCH] [Updated] " LaszloGombos
2022-12-13 23:02 ` LaszloGombos
2022-12-13 23:59 ` LaszloGombos
2022-12-14 23:48 ` LaszloGombos
2022-12-15 11:44 ` LaszloGombos
2022-12-15 13:34 ` LaszloGombos
2022-12-15 13:55 ` LaszloGombos
2022-12-18 20:01 ` LaszloGombos
2022-12-18 23:17 ` LaszloGombos
2022-12-20 14:53 ` LaszloGombos
2022-12-23 18:21 ` LaszloGombos
2023-01-04  2:40 ` LaszloGombos
2023-01-06 15:13 ` zdykstra
2023-01-17 13:08 ` ahesford [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230117130854.XIy_GE7dGbq_tggbXclFez0_DGvOEX5x_qhsyPuD5OQ@z \
    --to=ahesford@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).