[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171127082823.4d19c34e@xeon-e3>
Date: Mon, 27 Nov 2017 08:28:23 -0800
From: Stephen Hemminger <stephen@...workplumber.org>
To: David Miller <davem@...emloft.net>
Cc: netdev@...r.kernel.org
Subject: Re: [PATCH iproute2] drop support for DECnet
On Mon, 27 Nov 2017 23:04:45 +0900 (KST)
David Miller <davem@...emloft.net> wrote:
> From: Stephen Hemminger <stephen@...workplumber.org>
> Date: Sun, 26 Nov 2017 23:01:51 -0800
>
> > On Sun, 26 Nov 2017 17:19:21 -0500 (EST)
> > David Miller <davem@...emloft.net> wrote:
> >
> >> From: Stephen Hemminger <stephen@...workplumber.org>
> >> Date: Sun, 26 Nov 2017 12:11:18 -0800
> >>
> >> > Nothing has been done in Linux to maintain DECnet
> >> > for years. The code is buggy and does not support net namespace.
> >> > This patch removes all support of it from iproute2
> >> >
> >> > Signed-off-by: Stephen Hemminger <stephen@...workplumber.org>
> >>
> >> Even if decnet had been moved to staging/ (which it hasn't) I'd say
> >> this is entirely premature Stephen.
> >>
> >> As long as the decnet code is upstream, you can't just yank away
> >> support from the tooling.
> >
> > I agree that it is probably too early to remove support completely.
> > Instead, why not just mark IPX and DecNET as deprecated and warn users
> > for a couple of releases.
>
> People are using decnet.
>
> Last time I broke it there were users who complained.
What about IPX?
Powered by blists - more mailing lists