On Wed, Oct 23, 2013 at 8:04 AM, Yann Ylavic <ylavic....@gmail.com> wrote: > Should I continue this way? Simply to propose patches?
Sorry for not following up earlier. The patches are very much appreciated. But bite-sized ones are much easier for others to review. This might often mean fixing the rough corners of existing code in 1 pass, refactoring with no behavior change in another pass, then finally putting in the new stuff (just as a high level example). >> 1) add r->footers_in and use it in 2.2 and up by default > Do that mean no API/ABI change ? In the sense that it needs to be backportable, yes -- but it will mean a behavior change to "existing" APIs. Depends on how you interpret it I guess, but I think the confusion over trailers/headers is something that needs to be forcible corrected in those service releases. Thanks again for the help!
