From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 720b55a5a485d53b042bbf9c6e7e84e2d515b0bf
Date: Tue, 12 Aug 2025 06:26:10 +0000 (UTC) [thread overview]
Message-ID: <4c1M2p3NTfz2xHR@people01.haj.ipfire.org> (raw)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via 720b55a5a485d53b042bbf9c6e7e84e2d515b0bf (commit)
from 30cae58dd0be39699a95473e4abdbaace1d2f15f (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 720b55a5a485d53b042bbf9c6e7e84e2d515b0bf
Author: Arne Fitzenreiter <arne_f@ipfire.org>
Date: Tue Aug 12 07:22:08 2025 +0200
udev: fix rootfile on riscv
Signed-off-by: Arne Fitzenreiter <arne_f@ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/common/riscv64/udev | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/rootfiles/common/riscv64/udev b/config/rootfiles/common/riscv64/udev
index d329dffee..1e7814320 100644
--- a/config/rootfiles/common/riscv64/udev
+++ b/config/rootfiles/common/riscv64/udev
@@ -48,7 +48,7 @@ lib/udev/hwdb.d
lib/udev/iocost
lib/udev/mtd_probe
lib/udev/network-aqm
-lib/udev/network-hotplug-bridges
+lib/udev/network-hotplug-master
lib/udev/network-hotplug-rename
lib/udev/network-hotplug-vlan
lib/udev/network-offloading
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2025-08-12 6:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4c1M2p3NTfz2xHR@people01.haj.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.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