From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22427 invoked by alias); 26 May 2014 08:02:32 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 22408 invoked by uid 89); 26 May 2014 08:02:32 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.2 X-Spam-User: qpsmtpd, 2 recipients X-HELO: mx2.suse.de Received: from cantor2.suse.de (HELO mx2.suse.de) (195.135.220.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (CAMELLIA256-SHA encrypted) ESMTPS; Mon, 26 May 2014 08:02:30 +0000 Received: from relay1.suse.de (charybdis-ext.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 1FD62AC14; Mon, 26 May 2014 08:02:27 +0000 (UTC) Message-ID: <5382F50E.7040702@suse.com> Date: Mon, 26 May 2014 09:59:00 -0000 From: Andreas Jaeger User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Siddhesh Poyarekar CC: Siddhesh Poyarekar , GNU C Library , gdb@sourceware.org, carlos@redhat.com, fche@redhat.com, gbenson@redhat.com Subject: Re: patchwork.sourceware.org is live! References: <20140523211338.GK12497@spoyarek.pnq.redhat.com> <5382E7F2.4020506@suse.com> <5382EF22.4060705@suse.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-SW-Source: 2014-05/txt/msg00064.txt.bz2 On 05/26/2014 09:52 AM, Siddhesh Poyarekar wrote: > On 26 May 2014 13:07, Andreas Jaeger wrote: >> >> What happens if one person says "fine" while another one disagrees? Is >> Accepted then the right state for this? > > The first reviewer sets 'Accepted' (assuming she doesn't need another > reviewer to validate) and if another reviewer disagrees then he can > set the status back to 'Under Review'. if he agrees, then there's no > need to change any status. > >> Could you write up a workflow: Live of a patch, something like: >> 1. Patch gets submitted, system puts patch into state NEW >> 2. Reviewer comments on it: >> a) Disagrees: Sets it to >> b) agrees: Sets it to >> c) Not a patch for glibc, set it to Not Applicable >> 3. Patch gets committed: Set it to Commited/Accepted > > That's a good idea. I have modified the current document[1] and also > added the Committed status to the document. Once we have consensus on > adding the new 'Committed' status, I'll also add it to patchwork. > > Siddhesh > [1] https://sourceware.org/glibc/wiki/Patch%20Review%20Workflow > thanks, that answers my current ;) questions nicely, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126