From: Stephen Hemminger <shemminger@vyatta.com>
To: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] iproute2 v2.6.26
Date: Fri, 25 Jul 2008 14:10:54 -0700 [thread overview]
Message-ID: <20080725141054.7e814236@extreme> (raw)
New version of iproute2 utilities that includes bug fixes and
support for all the new features in kernel 2.6.26.
Source: (note old developer.osdl.org address works as well)
http://devresources.linux-foundation.org/dev/iproute2/download/iproute2-2.6.26.tar.bz2
Git tree:
git://git.kernel.org/pub/scm/network/iproute2/iproute2.git
Changelog:
Andreas Henriksson (3):
Fix typos (syntax error) in ip(8) manpage.
document promote_secondaries
Add routel and routef man page.
Benjamin Thery (1):
iproute2: add support for IFLA_NET_NS_PID in ip link
Bertrand Jacquin (1):
netem: fix cross-compiling failure
Daniel Silverstone (1):
Avoid infinite loop in ip addr flush.
Herbert Xu (1):
xfrm: Allow replay setting
Patrick McHardy (1):
tc: don't set protococol field on filter delete
Rafael Almeida (1):
Fixed installation when changing DESTDIR
Stephen Hemminger (12):
Fix bad hash calculation because of signed address
Change formatting of u32 back to default
Use inet_pton to read ipv4 addresses
ematch related bugfix and cleanup
Update to 2.6.26-rc6 headers
use correct hz for rto,ato
Neighbor cache timer is in user hz
timers are in user hz
Fix array out of bounds problem
Add warning message when MAX_FIELDS reached
Update headers to 2.6.26
Update snapshot
Varun Chandramohan (1):
Display Correct Error For Addrlabel Info
Yu Zhiguo (1):
Fix generic_proc_open() of command 'nstat' and 'rtacct'
jamal (2):
Expose the filter protocol
Infrastructure for pretty printing
reply other threads:[~2008-07-25 21:10 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=20080725141054.7e814236@extreme \
--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