Lars Schneider [off-list ref] writes:
Nice catch. I'll fix that in the next iteration.
Is it OK if I send the next iteration soon or would you prefer
it if I wait until after 2.16 release?
Plus, is it ok to keep the base of the series or would you prefer
it if I rebase it to the latest master (because of a minor conflict)?
I do not see this topic as a fix for grave bug that needs to go to
older maintenance track---it is rather a new feature, isn't it? So
a rebased series that cleanly applies on top of 2.16 final would be
a reasonable way to go forward.
Thanks.