netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Xose Vazquez Perez <xose@wanadoo.es>
To: netdev@oss.sgi.com, hch@lst.de
Subject: Re: Why is ifenslave.c in the kernel tree?
Date: Sun, 22 Feb 2004 20:21:49 +0100	[thread overview]
Message-ID: <4039014D.8060202@wanadoo.es> (raw)

Christoph Hellwig wrote:

> Just looking over the 2.6.3 diffs I see that ifenslave is actively
> maintained in Documenation/ of the kernel tree.  Isn't that a _really_
> odd place for a userland tool?  We have a policy of not having any
> userland tools not used for building in the kernel tree, and especially
> none of the distributors will pick it up from there.

The best place could be net-tools package.

But it looks like net-tools is sloppy, last change was done around Apr-2001 !!

--
x86-64 GenuineIntel

             reply	other threads:[~2004-02-22 19:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-22 19:21 Xose Vazquez Perez [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-15 10:02 Why is ifenslave.c in the kernel tree? Christoph Hellwig

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=4039014D.8060202@wanadoo.es \
    --to=xose@wanadoo.es \
    --cc=hch@lst.de \
    --cc=netdev@oss.sgi.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).