From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree tag, v2.29-core184, created. 6d501c05583a4efa513ff4b04a48ef41d5e8170e
Date: Tue, 12 Mar 2024 11:31:09 +0000 [thread overview]
Message-ID: <4TvBKn1d09z2xhc@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 941 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 tag, v2.29-core184 has been created
at 6d501c05583a4efa513ff4b04a48ef41d5e8170e (commit)
- Log -----------------------------------------------------------------
commit 6d501c05583a4efa513ff4b04a48ef41d5e8170e
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sun Feb 18 11:38:29 2024 +0100
cpufrequtils: hide output on disabled cores.
We disable cores if the are affected by some cpu vulnerabilities
this cores report errors if you try to change the settings.
So only print the output for core0 and hide it for all cores.
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2024-03-12 11:31 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=4TvBKn1d09z2xhc@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