From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>,
techboard@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-techboard] [PATCH v2] doc: update contribution guideline for dependent work
Date: Fri, 5 Apr 2019 16:02:31 +0100 [thread overview]
Message-ID: <b577ea3f-81ee-63db-1edc-5bcc61fae98f@intel.com> (raw)
Message-ID: <20190405150231.NVbdiiowLUfV7nNgAVrD2RI0d4NuuO7_XVe1GTr6AIw@z> (raw)
In-Reply-To: <be959187-4f79-65a2-e513-0cba16810d0a@intel.com>
On 4/5/2019 4:00 PM, Ferruh Yigit wrote:
> On 5/24/2018 5:58 PM, Thomas Monjalon wrote:
>> 09/01/2018 16:44, Ferruh Yigit:
>>> +* If changes effect other parts of the project, update all those parts as well unless updating requires special knowledge.
>>> + For the cases where not all the effected code is updated, the submitter should ensure that changes don't break existing code.
>>
>> We should review it again in the technical board.
>> I think we should encourage asking for help to complete a patch
>> with community's help.
>
> self-nack
>
> This was process update patch, but it seems lack of consensus for now.
>
for reference, mentioned patch:
https://patches.dpdk.org/patch/33250/
next prev parent reply other threads:[~2019-04-05 15:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 19:59 [dpdk-dev] [PATCH] " Ferruh Yigit
2017-12-11 14:26 ` Mcnamara, John
2017-12-12 15:54 ` [dpdk-dev] [dpdk-techboard] " Olivier MATZ
2017-12-12 18:57 ` Ferruh Yigit
2017-12-13 8:55 ` Olivier MATZ
2018-01-09 15:44 ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2018-05-24 16:58 ` Thomas Monjalon
2019-04-05 15:00 ` Ferruh Yigit
2019-04-05 15:00 ` Ferruh Yigit
2019-04-05 15:02 ` Ferruh Yigit [this message]
2019-04-05 15:02 ` [dpdk-dev] [dpdk-techboard] " Ferruh Yigit
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=b577ea3f-81ee-63db-1edc-5bcc61fae98f@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=techboard@dpdk.org \
--cc=thomas@monjalon.net \
/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).