This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Setting up patchwork on sourceware


On 03/21/2014 12:30 PM, Joseph S. Myers wrote:
> On Fri, 21 Mar 2014, Siddhesh Poyarekar wrote:
> 
>> On Tue, Mar 18, 2014 at 11:20:14AM -0400, Carlos O'Donell wrote:
>>> Thanks. I'll copy-edit. Tell me when it's ready. 
>>
>> It is now:
>>
>> https://sourceware.org/glibc/wiki/Patch%20Review%20Workflow
> 
> What's the right state for "the patch was only ever an RFC or proof of 
> concept rather than proposed for inclusion as-is"?

If a patch was an RFC, one should mark it state=RFC, such that
other reviewers not interested in reviewing RFCs may ignore that
patch.

If a patch was an RFC, but meant for inclusion as-is if accepted,
then you could check it in if you had consensus, at which point
you'd mark it state=Accepted, otherwise state=Rejected, or 
if it needed work state=Changes Requested (and the author needs
to resubmit the new version).

Does that answer your question?

Cheers,
Carlos.
 


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]