Re: [dpdk-dev] [PATCH v2] doc: update contribution guideline for dependent work

2019-04-05 Thread Ferruh Yigit
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

Re: [dpdk-dev] [PATCH v2] doc: update contribution guideline for dependent work

2018-05-24 Thread Thomas Monjalon
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

[dpdk-dev] [PATCH v2] doc: update contribution guideline for dependent work

2018-01-09 Thread Ferruh Yigit
Changing some part of the libraries but not updating all dependent code cause maintenance problems. The update in the contribution guide practically suggest updating all dependent code. With the counter argument that sometimes it is not possible to know details of the dependent code and this prev