Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andreas Jaeger <aj@suse.com>
To: Siddhesh Poyarekar <siddhesh@redhat.com>, libc-alpha@sourceware.org
Cc: gdb@sourceware.org, carlos@redhat.com, fche@redhat.com,
	 gbenson@redhat.com
Subject: Re: patchwork.sourceware.org is live!
Date: Mon, 26 May 2014 07:29:00 -0000	[thread overview]
Message-ID: <5382E7F2.4020506@suse.com> (raw)
In-Reply-To: <20140523211338.GK12497@spoyarek.pnq.redhat.com>

On 05/23/2014 11:13 PM, Siddhesh Poyarekar wrote:
> Hi,
> 
> Frank and I have now completed migration of the patchwork test
> instance to patchwork.sourceware.org.  I posted a couple of sample
> patches to the script directly and they seem to work just fine.  All
> accounts that were on patchwork.siddhesh.in should continue to work in
> the same manner on this instance.
> 
> I urge all glibc maintainers to please sign up and give it a spin.  As
> of now, Carlos and I have admin rights for glibc and Gary for gdb, so
> one of us should be able to add you to the project after you sign up,
> after which you can change patch state.  Once that is done, please
> close patches you know you have already pushed into master.
> 
> Please also take time to review the workflow for patch reviews:
> 
> https://sourceware.org/glibc/wiki/Patch%20Review%20Workflow

I have one question:

A patch that is merged, should have "Accepted", correct? so, patches
that are already committed should be changed to have this...

If i just comment on a patch with a "Looks fine", should I say "Under
Review" - and then the submitter sets this to "Accepted"?

Please document this workflow a bit better, it's confusing to me...

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


  parent reply	other threads:[~2014-05-26  7:06 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 [this message]
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
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=5382E7F2.4020506@suse.com \
    --to=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