Suggest "Dropped" state for patchwork.

[Carlos O'Donell]

Siddhesh,

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?

Cheers,
Carlos.