On 2018-03-03 02:00:46 +0100, Tomas Vondra wrote: > That is somewhat misleading, I think. You're right the last version was > submitted on 2018-01-19, but the next review arrived on 2018-01-31, i.e. > right at the end of the CF. So it's not like the patch was sitting there > with unresolved issues. Based on that review the patch was marked as RWF > and thus not moved to 2018-03 automatically.
I don't see how this changes anything. - Andres