Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh.poyarekar@gmail.com>
To: Andreas Jaeger <aj@suse.com>
Cc: Siddhesh Poyarekar <siddhesh@redhat.com>,
	GNU C Library <libc-alpha@sourceware.org>,
	gdb@sourceware.org, 	carlos@redhat.com, fche@redhat.com,
	gbenson@redhat.com
Subject: Re: patchwork.sourceware.org is live!
Date: Mon, 26 May 2014 08:02:00 -0000	[thread overview]
Message-ID: <CAAHN_R0GhZvqUDEN7e3DS2Y7b7W752oJabgET-nu6Oq8LJaeTA@mail.gmail.com> (raw)
In-Reply-To: <5382EF22.4060705@suse.com>

On 26 May 2014 13:07, Andreas Jaeger <aj@suse.com> 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
-- 
http://siddhesh.in


  reply	other threads:[~2014-05-26  7:52 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-23 21:12 Siddhesh Poyarekar
2014-05-24  3:20 ` Siddhesh Poyarekar
2014-05-24  4:02   ` David Miller
2014-05-24  7:28   ` Eli Zaretskii
2014-05-26  7:06     ` Siddhesh Poyarekar
2014-05-26  7:29 ` Andreas Jaeger
2014-05-26  7:37   ` Siddhesh Poyarekar
2014-05-26  7:52     ` Andreas Jaeger
2014-05-26  8:02       ` Siddhesh Poyarekar [this message]
2014-05-26  9:59         ` Andreas Jaeger
2014-05-26 10:41           ` Ondřej Bílka
2014-05-26 11:05             ` Siddhesh Poyarekar
2014-05-26 14:31               ` Ondřej Bílka
2014-05-30  2:59             ` Samuel Bronson
2014-05-30  8:36               ` Siddhesh Poyarekar
2014-05-30  8:45                 ` Pedro Alves
2014-05-30  8:55                   ` Pedro Alves
2014-05-30 14:38                     ` Siddhesh Poyarekar
2014-06-05 11:36                       ` Pedro Alves
2014-06-05 11:51                         ` Siddhesh Poyarekar
2014-06-04 10:28                 ` Ondřej Bílka
2014-05-26 10:21 ` Florian Weimer
2014-05-26 11:18   ` Carlos O'Donell
2014-05-26 15:09 ` Andreas Jaeger
2014-05-27  6:22   ` Carlos O'Donell
2014-05-27  6:27 ` Thomas Schwinge
2014-05-27  6:53   ` Siddhesh Poyarekar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAAHN_R0GhZvqUDEN7e3DS2Y7b7W752oJabgET-nu6Oq8LJaeTA@mail.gmail.com \
    --to=siddhesh.poyarekar@gmail.com \
    --cc=aj@suse.com \
    --cc=carlos@redhat.com \
    --cc=fche@redhat.com \
    --cc=gbenson@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=libc-alpha@sourceware.org \
    --cc=siddhesh@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox