On Sat, 5 Jan 2013, Jim Jagielski wrote:
I haven't created the patch yet... it seems backwards to generate a backport patchset unless what is currently in trunk is OK. There were some suggestions for improvement made regarding the 2.4 backport that ideally would have been noted and addressed in trunk first. I just want to avoid another go-around ;)
Would it be an option to let the changes sit in trunk for a while longer and not include them in 2.4.4? We could still aim for a 2.4.5 not too long after, e.g. before ApacheCon.
