From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. e4edd42d8987550fcf2d242b922731e7958f7b09
Date: Tue, 19 Mar 2013 23:47:53 +0100 [thread overview]
Message-ID: <20130319224753.E6A3B20141@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1454 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 e4edd42d8987550fcf2d242b922731e7958f7b09 (commit)
from 2652a1fed890b14ad44ce7764e51b398eb15c02e (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 e4edd42d8987550fcf2d242b922731e7958f7b09
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Tue Mar 19 23:46:43 2013 +0100
iproute2: Rebuild with new iptables.
iproute2 links against libiptables, which had a version
bump, so we need to rebuild against the new version.
-----------------------------------------------------------------------
Summary of changes:
iproute2/iproute2.nm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/iproute2/iproute2.nm b/iproute2/iproute2.nm
index 433e35f..c466ebc 100644
--- a/iproute2/iproute2.nm
+++ b/iproute2/iproute2.nm
@@ -5,7 +5,7 @@
name = iproute2
version = 3.5.1
-release = 1
+release = 2
groups = Networking/Tools
url = http://www.linuxfoundation.org/en/Net:Iproute2
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2013-03-19 22:47 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=20130319224753.E6A3B20141@argus.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