From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Neil Horman <nhorman@tuxdriver.com>,
Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
Markos Chandras <mchandras@suse.de>,
"Panu Matilainen" <pmatilai@redhat.com>
Subject: Re: [dpdk-dev] RFC: DPDK Long Term Support
Date: Tue, 7 Jun 2016 16:21:21 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE20257D07D@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <20160606134742.GA3867@hmsreliant.think-freely.org>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Neil Horman
> Sent: Monday, June 6, 2016 2:48 PM
> To: Thomas Monjalon <thomas.monjalon@6wind.com>
> Cc: dev@dpdk.org; Mcnamara, John <john.mcnamara@intel.com>; Christian
> Ehrhardt <christian.ehrhardt@canonical.com>; Markos Chandras
> <mchandras@suse.de>; Panu Matilainen <pmatilai@redhat.com>
> Subject: Re: [dpdk-dev] RFC: DPDK Long Term Support
>
> While I don't disagree with that statement (LTS does provide both of those
> things if the maintainer does it properly), I'm forced to ask the
> question, before we solve this problem in a new way, lets ask why the
> existing way isn't being used. Do developers just not care about
> backwards compatibility? Is the process to hard? Something else? I
> really don't like the idea of abandoning what currently exists to replace
> it with something else, without first addressing why what we have isn't
> working.
Hi Neil,
I think these questions around why the current ABI policy isn't working
(or at least not working well) and how it can be fixed are worth raising
as a new discussion.
John.
--
next prev parent reply other threads:[~2016-06-07 16:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 15:07 Mcnamara, John
2016-06-03 16:05 ` Thomas Monjalon
2016-06-06 11:49 ` Yuanhan Liu
2016-06-06 13:31 ` Thomas Monjalon
2016-06-06 14:14 ` Yuanhan Liu
2016-06-06 14:23 ` Thomas Monjalon
2016-06-07 13:17 ` Mcnamara, John
2016-06-03 18:17 ` Matthew Hall
2016-06-07 12:53 ` Mcnamara, John
2016-06-05 18:15 ` Neil Horman
2016-06-06 9:27 ` Thomas Monjalon
2016-06-06 13:47 ` Neil Horman
2016-06-06 14:21 ` Thomas Monjalon
2016-06-06 15:07 ` Neil Horman
2016-06-07 16:21 ` Mcnamara, John [this message]
2016-06-07 15:55 ` Mcnamara, John
2016-06-06 13:44 ` Nirmoy Das
2016-06-06 14:16 ` Yuanhan Liu
2016-06-07 12:36 ` Christian Ehrhardt
2016-06-07 19:39 ` Martinx - ジェームズ
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=B27915DBBA3421428155699D51E4CFE20257D07D@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=christian.ehrhardt@canonical.com \
--cc=dev@dpdk.org \
--cc=mchandras@suse.de \
--cc=nhorman@tuxdriver.com \
--cc=pmatilai@redhat.com \
--cc=thomas.monjalon@6wind.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).