From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Olivier Matz <olivier.matz@6wind.com>, dev@dpdk.org
Cc: techboard@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-techboard] next techboard meeting 2018-02-14
Date: Tue, 13 Feb 2018 14:30:38 +0000 [thread overview]
Message-ID: <5dd99c58-6fae-796f-c8e6-fcfbbe576acd@intel.com> (raw)
In-Reply-To: <20180213103723.egerwii54nctt3id@platinum>
On 2/13/2018 10:37 AM, Olivier Matz wrote:
> Hi,
>
> The next Technical Board meeting will happen on IRC freenode #dpdk-board
> this wednesday 14 february 3pm UTC.
>
> You will find links to the agenda and previous meetings on this page:
> http://dpdk.org/dev/techboard-minutes
> The last one is not yet on the website:
> http://dpdk.org/ml/archives/dev/2018-February/090698.html
>
> Please send on any items requiring techboard attention.
Can we discuss following process patch:
https://dpdk.org/dev/patchwork/patch/33250/
Mainly the issue is how to approach a patch that effects other parts of the
DPDK, who should update those dependent parts, the initiator of the feature or
the maintainer of those parts?
Two opposed arguments on issue:
- If initiator doesn't fix the dependent code, somebody needs to follow the
dependent parts to do the work, which is a maintenance cost keep growing by time.
- If initiator has to do the all work, this is too much work for initiator and
may prevent improvements because of too much work, or because of missing
knowledge in dependent parts.
Thanks,
ferruh
>
> Thanks,
> Olivier
>
prev parent reply other threads:[~2018-02-13 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 10:37 [dpdk-dev] " Olivier Matz
2018-02-13 11:51 ` [dpdk-dev] [dpdk-techboard] " Thomas Monjalon
2018-02-13 14:30 ` Ferruh Yigit [this message]
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=5dd99c58-6fae-796f-c8e6-fcfbbe576acd@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.com \
--cc=techboard@dpdk.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).