From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. ec9a3ffe9c072fef0cae4b96c136e8512851ae29
Date: Fri, 03 Jun 2016 16:32:34 +0100 [thread overview]
Message-ID: <20160603153235.3A5781078E81@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1676 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 ec9a3ffe9c072fef0cae4b96c136e8512851ae29 (commit)
from b449c308baf63df68ab81a62cbdd89e64da71ab9 (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 ec9a3ffe9c072fef0cae4b96c136e8512851ae29
Author: Alexander Marx <alexander.marx(a)ipfire.org>
Date: Thu Jun 2 14:37:35 2016 +0200
nftables: Update to latest snapshot 20160602
Signed-off-by: Alexander Marx <alexander.marx(a)ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
nftables/nftables.nm | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Difference in files:
diff --git a/nftables/nftables.nm b/nftables/nftables.nm
index bd100df..f8a97d0 100644
--- a/nftables/nftables.nm
+++ b/nftables/nftables.nm
@@ -5,8 +5,8 @@
name = nftables
version = 0.100
-snapshot = 20150531
-release = 3.%{snapshot}
+snapshot = 20160602
+release = 1.%{snapshot}
thisapp = %{name}-%{snapshot}
groups = Networking/Tools
@@ -33,7 +33,7 @@ build
gmp-devel
libtool
libmnl-devel
- libnftnl-devel >= 1.0.3-1.20150531
+ libnftnl-devel >= 1.0.5
readline-devel
end
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2016-06-03 15:32 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=20160603153235.3A5781078E81@git01.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