Suggest "Dropped" state for patchwork.

[Siddhesh Poyarekar]

On Fri, Nov 28, 2014 at 01:09:37PM -0500, Carlos O'Donell wrote:
> While doing more and more patcwork work I noticed a problem
> I had with the `Rejected` state.
> 
> The more rejected patches you have the harder it becomes to
> review the rejected patch list to see which patches you want
> to do over again with a different approach.
> 
> I have updated "Patch Review Workflow" with a "Dropped"
> state that developers can use to indicate they don't plan
> to do any more work on the patch. Either "Rejected" or
> "Dropped" are end states, but "Dropped" allows the developer
> to also use patchwork as a todo list, not just the maintainers.
> And as maintainers we all have our own patches to track.
> 
> https://sourceware.org/glibc/wiki/Patch Review Workflow
> 
> Should we add a "Dropped" state?

I think you'll have the same problem with the Dropped state - the more
dropped patches you have, the harder it becomes to review the list to
see which patches you want to do over again with a different approach.

Siddhesh
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/libc-alpha/attachments/20141129/789e5456/attachment.sig>