Jeff Felchner <jfelchner1@xxxxxxxxx> writes: > Hey all, I assumed this was going to be in 2.18, but I'm still having the same issue. What's the plan for release of this? You assumed wrong ;-) A patch written on June 11th that is already deep into pre-release freeze, unless it is about fixing a regression during the same cycle, would never be in the release tagged on 21st. It is already a part of the 'master' branch after v2.18, so v2.19 would be the first feature release that would see it (unless we discover problems in that change and need to revert it, that is).
