[RFC] Setting the correct Patchwork status

[Carl-Daniel Hailfinger]

Hi,

I'd like to get some input on using the correct "patch state" in Patchwork.

1. Patches which have been acked and are waiting for commit.
2. Patches which are not intended for merging, but which should stay
easily available in case someone needs them. This includes debug patches
and emergency recovery patches.

For type 1, I think either "Awaiting upstream" or "Under review" are OK.
We could add an additional state "Waiting for commit".
For type 2, it is a lot more difficult. "Not applicable" is for patches
sent to the wrong list. "Rejected" and "RFC" don't fit either. What
about an additional state "Not for merging"?

Regards,
Carl-Daniel

[Maciej Pijanka]

On wto, 24 lis 2009, Carl-Daniel Hailfinger wrote:
> Hi,
>
> I'd like to get some input on using the correct "patch state" in Patchwork.
> Patches which have been acked and are waiting for commit.
> Patches which are not intended for merging, but which should stay
>
> easily available in case someone needs them. This includes debug patches
> and emergency recovery patches.
> For type 2, it is a lot more difficult. "Not applicable" is for patches
> sent to the wrong list. "Rejected" and "RFC" don't fit either. What
> about an additional state "Not for merging"?

Saved for reference? or For reference only ?
> Regards,
> Carl-Daniel