From: David Ahern <dsahern@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: Can decnet be deprecated?
Date: Sat, 24 Nov 2018 18:35:14 -0700 [thread overview]
Message-ID: <141bd0c0-3e4b-8730-a6b2-4c5be7d25138@gmail.com> (raw)
In-Reply-To: <20181124.172509.1739636063027441678.davem@davemloft.net>
On 11/24/18 6:25 PM, David Miller wrote:
> From: David Ahern <dsahern@gmail.com>
> Date: Sat, 24 Nov 2018 17:12:48 -0700
>
>> IPX was moved to staging at the end of last year. Can decnet follow
>> suit? git log seems to indicate no active development in a very long time.
>
> Last time I tried to do that someone immediately said on the list
> "Don't, we're using that!"
>
Ugh, I was afraid of that response. I guess I will have to work around
it for the neighbor changes.
next prev parent reply other threads:[~2018-11-25 12:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-25 0:12 Can decnet be deprecated? David Ahern
2018-11-25 1:25 ` David Miller
2018-11-25 1:35 ` David Ahern [this message]
2018-11-25 11:30 ` Bjørn Mork
2018-11-25 18:31 ` David Miller
2018-11-25 11:38 ` Loganaden Velvindron
2018-11-27 0:34 ` Stephen Hemminger
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=141bd0c0-3e4b-8730-a6b2-4c5be7d25138@gmail.com \
--to=dsahern@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/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).