From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. de80f74152e08080c5f302cf56cab6daa79169b4
Date: Wed, 27 May 2026 10:46:50 +0000 (UTC) [thread overview]
Message-ID: <4gQRBf4PsMz2xKs@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 de80f74152e08080c5f302cf56cab6daa79169b4 (commit)
from 9a45c759d6367516bfb0c9a5516a50fc7920c5e5 (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 de80f74152e08080c5f302cf56cab6daa79169b4
Author: Matthias Fischer <matthias.fischer@ipfire.org>
Date: Sun May 24 15:44:50 2026 +0200
libcap-ng 0.9.3: Update for rootfile
Signed-off-by: Matthias Fischer <matthias.fischer@ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/common/libcap-ng | 2 ++
1 file changed, 2 insertions(+)
Difference in files:
diff --git a/config/rootfiles/common/libcap-ng b/config/rootfiles/common/libcap-ng
index 33e96b97a..8677e42ab 100644
--- a/config/rootfiles/common/libcap-ng
+++ b/config/rootfiles/common/libcap-ng
@@ -12,6 +12,8 @@ usr/lib/libdrop_ambient.so.0
usr/lib/libdrop_ambient.so.0.0.0
#usr/lib/pkgconfig/libcap-ng.pc
#usr/share/aclocal/cap-ng.m4
+#usr/share/bash-completion
+#usr/share/bash-completion/completions
#usr/share/bash-completion/completions/libcap-ng.bash_completion
#usr/share/man/man3/capng_apply.3
#usr/share/man/man3/capng_apply_caps_fd.3
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2026-05-27 10:46 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=4gQRBf4PsMz2xKs@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