This is the mail archive of the
mailing list for the glibc project.
Re: Suggest "Dropped" state for patchwork.
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Siddhesh Poyarekar <siddhesh at redhat dot com>
- Cc: GNU C Library <libc-alpha at sourceware dot org>, "Joseph S. Myers" <joseph at codesourcery dot com>
- Date: Fri, 28 Nov 2014 21:23:30 -0500
- Subject: Re: Suggest "Dropped" state for patchwork.
- Authentication-results: sourceware.org; auth=none
- References: <5478BA61 dot 1040007 at redhat dot com> <20141129011720 dot GJ24022 at spoyarek dot pnq dot redhat dot com> <54792C16 dot 3030403 at redhat dot com> <20141129022004 dot GN24022 at spoyarek dot pnq dot redhat dot com>
On 11/28/2014 09:20 PM, Siddhesh Poyarekar wrote:
> On Fri, Nov 28, 2014 at 09:14:46PM -0500, Carlos O'Donell wrote:
>> You never review "Dropped" patches. You review "Rejected" patches and
>> move the ones you never want to see into "Dropped."
>> The question I want to answer is: Which of the recently rejected patches
>> do I need to work on?
>> Thus you review the "Rejected" patches, moving dropped ones to "Dropped"
>> and keeping the list of "Rejected" patches small for review.
>> Does that help clarify my need?
> OK, seems fine.
How do we add a new state?