From: Samuel Bronson <naesten@gmail.com>
To: gdb@sourceware.org
Cc: libc-alpha@sourceware.org
Subject: Re: patchwork.sourceware.org is live!
Date: Fri, 30 May 2014 02:59:00 -0000 [thread overview]
Message-ID: <87d2ewdo60.fsf@naesten.mooo.com> (raw)
In-Reply-To: <20140526102052.GA18682@domone>
OndÅej BÃlka <neleai@seznam.cz> writes:
> On Mon, May 26, 2014 at 10:02:22AM +0200, Andreas Jaeger wrote:
>> On 05/26/2014 09:52 AM, Siddhesh Poyarekar wrote:
>> > 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
>> >
Are there any objections to the new state?
> 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 ...
--
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!
next prev parent reply other threads:[~2014-05-30 1:57 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 [this message]
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=87d2ewdo60.fsf@naesten.mooo.com \
--to=naesten@gmail.com \
--cc=gdb@sourceware.org \
--cc=libc-alpha@sourceware.org \
/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