netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: netdev@vger.kernel.org, linux-net@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] iproute 2.6.32 released
Date: Sat, 26 Dec 2009 13:42:31 -0800	[thread overview]
Message-ID: <20091226134231.06bf822e@nehalam> (raw)
In-Reply-To: <8bd0f97a0912261338w62b810bdh3e660ae61b8ae975@mail.gmail.com>

On Sat, 26 Dec 2009 16:38:21 -0500
Mike Frysinger <vapier.adi@gmail.com> wrote:

> On Sat, Dec 26, 2009 at 16:36, Stephen Hemminger wrote:
> > On Sat, 26 Dec 2009 14:43:10 -0500
> > Mike Frysinger <vapier.adi@gmail.com> wrote:
> >
> >> On Sat, Dec 26, 2009 at 13:58, Stephen Hemminger wrote:
> >> > This version of iproute2 utilities includes the changes necessary to support all the features in
> >> > 2.6.32, but should be backward compatible with older releases. Lots of bug fixes and little
> >> > things, the main area of change is around the always problematic 'ip route flush' interface.
> >> >
> >> > The tar ball is available at:
> >> >  http://devresources.linuxfoundation.org/dev/iproute2/download/iproute2-2.6.31.tar.bz2
> >>
> >> URL and git says 2.6.31, but subject says 2.6.32, so i'm guessing
> >> subject is the typoe
> >
> > Actually, the url is typo
> 
> there is no 2.6.32 tarball in the dir indicated by the URL.  there is
> however a 2.6.31 tarball dated today.
> -mike

The name is wrong but the code is up to date with 2.6.32.


-- 

      reply	other threads:[~2009-12-26 21:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-26 18:58 [ANNOUNCE] iproute 2.6.32 released Stephen Hemminger
2009-12-26 19:43 ` Mike Frysinger
2009-12-26 21:36   ` Stephen Hemminger
2009-12-26 21:38     ` Mike Frysinger
2009-12-26 21:42       ` Stephen Hemminger [this message]

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=20091226134231.06bf822e@nehalam \
    --to=shemminger@vyatta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=vapier.adi@gmail.com \
    /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).