Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@redhat.com>
To: Samuel Bronson <naesten@gmail.com>
Cc: libc-alpha@sourceware.org, gdb@sourceware.org
Subject: Re: patchwork.sourceware.org is live!
Date: Fri, 30 May 2014 08:36:00 -0000	[thread overview]
Message-ID: <20140530030029.GN12497@spoyarek.pnq.redhat.com> (raw)
In-Reply-To: <87d2ewdo60.fsf@naesten.mooo.com>

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

On Thu, May 29, 2014 at 09:56:55PM -0400, Samuel Bronson wrote:
> Are there any objections to the new state?

None so far.  I have added it to patchwork now.  I have not yet made
'Accepted' an 'Action Required' state because that will clutter the
view; I'll do it when I get explicit blessings from more maintainers.

> > That should be set automatically. I use a following script to detect
> > commited patches.
> 
> If there are no objections, I guess the script will need to be changed
> to put patches in the "Committed" state instead of the "Accepted" state?
> 
> However, really I'd prefer if it could give some indication as to
> *which* commit(s) the patch was committed as, and it doesn't look like
> this is viable with the current approach, since you seem to just test if
> each patch can be applied backwards to HEAD.
> 
> Oh, but now I notice that that *particular* script is glibc-only anyway,
> so maybe I don't really care that much ...

That particular script was just an example, so ideas for automating
this are still welcome.

Siddhesh

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

  reply	other threads:[~2014-05-30  2:59 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 [this message]
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=20140530030029.GN12497@spoyarek.pnq.redhat.com \
    --to=siddhesh@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=libc-alpha@sourceware.org \
    --cc=naesten@gmail.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