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. 271e3b6a0ea30fb01b1b9705617db8b276c314f9
Date: Sun, 09 Jul 2023 10:21:59 +0000 [thread overview]
Message-ID: <4QzNTz2RSYz2xgm@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1689 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 271e3b6a0ea30fb01b1b9705617db8b276c314f9 (commit)
from 00ff498eb5c6bf791b44a539890871c088e84b65 (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 271e3b6a0ea30fb01b1b9705617db8b276c314f9
Author: Peter Müller <peter.mueller(a)ipfire.org>
Date: Sun Jul 9 10:21:24 2023 +0000
util-linux: Hrmpf, fix aarch64 rootfile again
My fault, again. :-/
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/common/aarch64/util-linux | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/rootfiles/common/aarch64/util-linux b/config/rootfiles/common/aarch64/util-linux
index 661e6a5a8..f241a7d89 100644
--- a/config/rootfiles/common/aarch64/util-linux
+++ b/config/rootfiles/common/aarch64/util-linux
@@ -320,7 +320,7 @@ usr/sbin/rtcwake
#usr/share/man/man8/agetty.8
#usr/share/man/man8/blkdiscard.8
#usr/share/man/man8/blkid.8
-+usr/share/man/man8/blkpr.8
+#usr/share/man/man8/blkpr.8
#usr/share/man/man8/blkzone.8
#usr/share/man/man8/blockdev.8
#usr/share/man/man8/cfdisk.8
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2023-07-09 10:21 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=4QzNTz2RSYz2xgm@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