From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Michal Kochanowicz <michal@michal.waw.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: What to use with 2.6.x instead of iproute2?
Date: Mon, 29 Sep 2003 11:17:16 -0400 [thread overview]
Message-ID: <3F784CFC.30103@nortelnetworks.com> (raw)
In-Reply-To: 20030927151935.GD5956@wieszak.lan
Michal Kochanowicz wrote:
> Hi!
>
> It seems that iproute2 is not maintained any more and it doesn't build
> with kernel 2.6.0-test5.
Is Alexey still the iproute2 maintainer? Has anyone sent him a patch
for 2.6?
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next prev parent reply other threads:[~2003-09-29 15:18 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 [this message]
2003-09-29 15:29 ` Kevin P. Fleming
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=3F784CFC.30103@nortelnetworks.com \
--to=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;
as well as URLs for NNTP newsgroup(s).