> I guess it depends on how risky the patch is, while reorg.c affects only a > few targets, they still include some primary targets. If it is not a > regression from 4.6.0 and the fix isn't very obviously safe, it would > probably be better to postpone it for 4.6.2 (though, I think CPU cycles > wouldn't be wasted by preparing a fix for 4.6.2).
I think it is as obviously safe as a reorg.c patch can be so I'm going to test it (on the branch) and post it afterward, but it will be your call of course. -- Eric Botcazou
