From: "Kevin P. Fleming" <kpfleming@backtobasicsmgmt.com>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: Michal Kochanowicz <michal@michal.waw.pl>, linux-kernel@vger.kernel.org
Subject: Re: What to use with 2.6.x instead of iproute2?
Date: Mon, 29 Sep 2003 08:29:07 -0700 [thread overview]
Message-ID: <3F784FC3.5090301@backtobasicsmgmt.com> (raw)
In-Reply-To: <3F784CFC.30103@nortelnetworks.com>
Chris Friesen wrote:
> Is Alexey still the iproute2 maintainer? Has anyone sent him a patch
> for 2.6?
>
There are no patches to iproute2 required to get it to compile against
2.6 headers; the only patch required was to linux/netdevice.h, which
has been included in 2.6.0-test6.
However, it would be wonderful if someone knowledgeable could take
over maintainership of iproute2 if Alexey can no longer do it. It's in
a sorry state at the moment, and most distros ship significantly
patched versions.
prev parent reply other threads:[~2003-09-29 15:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-27 15:19 What to use with 2.6.x instead of iproute2? Michal Kochanowicz
2003-09-27 16:11 ` Kevin P. Fleming
2003-09-29 15:17 ` Chris Friesen
2003-09-29 15:29 ` Kevin P. Fleming [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=3F784FC3.5090301@backtobasicsmgmt.com \
--to=kpfleming@backtobasicsmgmt.com \
--cc=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal@michal.waw.pl \
/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