Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Thomas Schwinge <thomas@codesourcery.com>
To: Siddhesh Poyarekar <siddhesh@redhat.com>, <gdb@sourceware.org>,
	<libc-alpha@sourceware.org>
Cc: <carlos@redhat.com>, <fche@redhat.com>, <gbenson@redhat.com>
Subject: Re: patchwork.sourceware.org is live!
Date: Tue, 27 May 2014 06:27:00 -0000	[thread overview]
Message-ID: <87a9a3spu4.fsf@kepler.schwinge.homeip.net> (raw)
In-Reply-To: <20140523211338.GK12497@spoyarek.pnq.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]

Hi!

On Sat, 24 May 2014 02:43:38 +0530, Siddhesh Poyarekar <siddhesh@redhat.com> wrote:
> patchwork.sourceware.org

> close patches you know you have already pushed into master.

Does that mean changing the state to »Accepted« (or »Committed«, once
that has been added), or ticking the »Archived« box, or both?  What's the
meaning of the »Archived« box?

> Please also take time to review the workflow for patch reviews:
> 
> https://sourceware.org/glibc/wiki/Patch%20Review%20Workflow

So, does patchwork's »Delegate to« Patch Property equal Bugzilla's
»Assigned To« field?  And, it is not totally clear to my why the Patch
Review Workflow suggests to »not change the status of the patch« if
»changing the Delegate to value to their patchwork username«?

"In a perfect world", after a patch review, during which »Delegate to«
has been set to the reviewer(s), should it then be changed to the person
who is responsible for committing the patch (which may be the submitter,
or the reviewer, or someone else), together with changing the state to
»Accepted«?


Grüße,
 Thomas

[-- Attachment #2: Type: application/pgp-signature, Size: 472 bytes --]

  parent reply	other threads:[~2014-05-27  6:22 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
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 [this message]
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=87a9a3spu4.fsf@kepler.schwinge.homeip.net \
    --to=thomas@codesourcery.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