From: Stephen Hemminger <shemminger@vyatta.com>
To: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] iproute2 3.4.0
Date: Mon, 21 May 2012 14:37:40 -0700 [thread overview]
Message-ID: <20120521143740.2f6c0ecd@nehalam.linuxnetplumber.net> (raw)
To go with kernel release of 3.4 here is the update to
iproute2. There wasn't a lot new features in this release, mostly
manual pages and cleanups.
Source:
http://www.kernel.org/pub/linux/utils/net/iproute2/iproute2-3.4.0.tar.gz
Repository:
git://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git
Changes:
Andreas Henriksson (1):
iproute2: trivial fix of ip link syntax in manpage
Chris Elston (1):
iproute2: allow IPv6 addresses for l2tp local and remote parameters
Christoph J. Thompson (4):
iproute2 - Don't hardcode the path to config files
iproute2 - Split up cflags
iproute2 - Split up manual page installation
iproute2 - Fix up and simplify variables pointing to install directories
Eric Dumazet (1):
Fix ss if INET_DIAG not enabled in kernel
Florian Westphal (1):
tc: man: choke counts packets, not bytes
James Chapman (1):
iproute2: add ip-l2tp man page
Jorge Boncompte [DTI2] (1):
iproute: show metrics as an unsigned value
João Valverde (1):
ipl2tp: allow setting session interface name
Rose, Gregory V (1):
iproute2: Add netlink attribute to filter dump requests
Shan Wei (1):
ss: use new INET_DIAG_SKMEMINFO option to get more memory information for tcp socket
Stephen Hemminger (6):
Add ability to set link state with ip
Make link mode case independent
Convert to use rta_getattr_ functions
Merge in 3.3-rc2 kernel headers
Revert "iproute2: allow IPv6 addresses for l2tp local and remote parameters"
v3.4.0
Vijay Subramanian (1):
Update man8 Makefile
next reply other threads:[~2012-05-21 21:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 21:37 Stephen Hemminger [this message]
2012-05-21 21:48 ` [ANNOUNCE] iproute2 3.4.0 John Fastabend
2012-05-21 22:01 ` Stephen Hemminger
2012-05-21 22:02 ` John Fastabend
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=20120521143740.2f6c0ecd@nehalam.linuxnetplumber.net \
--to=shemminger@vyatta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).