From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. a54609626c4f45e00f8a45780ce553d1f60734d8
Date: Sun, 10 May 2020 18:37:17 +0000 [thread overview]
Message-ID: <49Kt8Y6zktz2xds@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1488 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 3.x development tree".
The branch, master has been updated
via a54609626c4f45e00f8a45780ce553d1f60734d8 (commit)
from 5d673af27fc2105b72af6bef16a68de333aa0fa7 (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 a54609626c4f45e00f8a45780ce553d1f60734d8
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Sun May 10 19:37:05 2020 +0100
libseccomp: Update to 2.4.3
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
libseccomp/libseccomp.nm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/libseccomp/libseccomp.nm b/libseccomp/libseccomp.nm
index 2be8e9730..2b6202e18 100644
--- a/libseccomp/libseccomp.nm
+++ b/libseccomp/libseccomp.nm
@@ -4,7 +4,7 @@
###############################################################################
name = libseccomp
-version = 2.4.0
+version = 2.4.3
release = 1
groups = System/Libraries
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2020-05-10 18:37 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=49Kt8Y6zktz2xds@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