From: "Peter Müller" <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 2f52d27a829a891b3cff549f2b0a0763915f8311
Date: Wed, 22 Jun 2022 12:27:16 +0000 [thread overview]
Message-ID: <4LSjLr2T7Zz2y7l@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1650 bytes --]
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 2f52d27a829a891b3cff549f2b0a0763915f8311 (commit)
from 54bd60b67b477e5d5814293a74086dff1c21ac69 (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 2f52d27a829a891b3cff549f2b0a0763915f8311
Author: Peter Müller <peter.mueller(a)ipfire.org>
Date: Wed Jun 22 12:27:02 2022 +0000
Core Update 169: Ship changed initscripts
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/169/filelists/files | 2 ++
1 file changed, 2 insertions(+)
Difference in files:
diff --git a/config/rootfiles/core/169/filelists/files b/config/rootfiles/core/169/filelists/files
index 44a68f28e..e4ae9beb5 100644
--- a/config/rootfiles/core/169/filelists/files
+++ b/config/rootfiles/core/169/filelists/files
@@ -7,7 +7,9 @@ etc/rc.d/helper/exoscale-setup
etc/rc.d/helper/gcp-setup
etc/rc.d/helper/oci-setup
etc/rc.d/init.d/localnet
+etc/rc.d/init.d/mountkernfs
etc/rc.d/init.d/ntp
+etc/rc.d/init.d/udev
etc/sysctl.conf
lib/firmware/amdgpu/aldebaran_mec2.bin
lib/firmware/amdgpu/aldebaran_mec.bin
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2022-06-22 12:27 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=4LSjLr2T7Zz2y7l@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