Hi,
I still think its better to say no way to all big patches. =)
Othervice if we do like this, we create a backdoor for people that
doesn't want's
to split up their patches or lack the knowledge how to do it.
Cheers,
Anders
On 23 November 2014 at 23:58, Maxim Uvarov maxim.uva...@linaro.org
On 11/24/2014 11:31 AM, Anders Roxell wrote:
Hi,
I still think its better to say no way to all big patches. =)
Othervice if we do like this, we create a backdoor for people that
doesn't want's
to split up their patches or lack the knowledge how to do it.
In case of API changes there may
Hello everybody,
Me, Anders and Mike discussed the best way to go in case if needed to
split huge patch on small ones for review. And for compilation it will
be needed to merge all small patches to single patch.
Typical situation in ODP might be like 3 patches:
1. API change.
2.
Thanks. I just re-submitted v3 of the buffer pool patch that fits this
model as a 3-part patch. Can we consider this RFC according to the above
criteria, or do I need to resubmit a v4 with just the name change?
Bill
On Sun, Nov 23, 2014 at 7:35 AM, Maxim Uvarov maxim.uva...@linaro.org
wrote:
On 11/23/2014 05:15 PM, Bill Fischofer wrote:
Thanks. I just re-submitted v3 of the buffer pool patch that fits
this model as a 3-part patch. Can we consider this RFC according to
the above criteria, or do I need to resubmit a v4 with just the name
change?
Bill
I think you can add RFC
