On Tue, Feb 16, 2016 at 11:12 PM, Pavel Stehule <pavel.steh...@gmail.com>
> 2016-02-17 3:19 GMT+01:00 Jim Nasby <jim.na...@bluetreble.com>:
>> On 2/16/16 12:38 AM, Michael Paquier wrote:
>>> When a patch with status "Ready for committer" on CF N is moved to CF
>>> (N+1), its status is automatically changed to "Needs Review". That's
>>> something to be aware of when cleaning up the CF app entries.
>> I agree with Alvarro; this seems like a bug to me. If a patch is ready
>> for committer in CF N, why would it suddenly not be ready in N+1?
> This behave is pretty unpleasant and frustrating.
Well, it's in no way a bug, because it's the behavior we agreed upon at the
That said, we can certainly reconsider that. Would we always copy the value
over? Even if it was, say, rejected? (so it would be copied to the new CF
but still marked rejected) Or is there a subset of behaviors you're looking