Hi David, On 03/09/2016 05:28 PM, Hunt, David wrote: >> Sorry, maybe I wasn't very clear in my previous messages. For me, the >> NEXT_ABI is not the proper solution because, as Panu stated, it makes >> the patch hard to read. My understanding of NEXT_ABI is that it should >> only be used if the changes are small enough. Duplicating the code with >> a big #ifdef NEXT_ABI is not an option to me either. >> >> So that's why the deprecation notice should be used instead. But in this >> case, it means that this patch won't be present in 16.04, but will be >> added in 16.07. >> > Sure, v4 will remove the NEXT_ABI patch , and replace it with just the > ABI break announcement for 16.07. For anyone who what's to try out the > patch, they can always get it from patchwork, but not as part 16.04.
I think it's better to have the deprecation notice in a separate mail, outside of the patch series, so Thomas can just apply this one and let the series pending for 16.07. Thanks, Olivier
