From: Gary Benson <gbenson@redhat.com>
To: Stan Shebs <stanshebs@earthlink.net>
Cc: gdb@sourceware.org
Subject: Re: Patchwork patch tracking system
Date: Thu, 17 Apr 2014 18:18:00 -0000 [thread overview]
Message-ID: <20140417135040.GA891@blade.nx> (raw)
In-Reply-To: <533F3713.40700@earthlink.net>
Hi Stan,
Sorry for the late reply, your message got lost in a bunch of
demangler issues :(
Stan Shebs wrote:
> On 4/2/14 3:08 AM, Gary Benson wrote:
> > Patchwork is a patch tracking system designed to help manage
> > contributions to open-source projects. The glibc maintainers have
> > been experimenting to see if it can meet their needs, and they've
> > very kindly added GDB to their test instance to allow us to trial
> > it too.
>
> I just heard about this last week, and it looks like a good idea!
>
> > Patchwork has been subscribed to gdb-patches for a couple of weeks
> > now, but I haven't updated any patches' statuses so there will be
> > some stale ones in there. Please feel free to update patches as
> > you see fit, this is a trial instance so don't worry about
> > breaking things!
>
> So if we try it and like it, how does one go about transitioning
> from "trial" to "real"?
I guess by the people doing the reviewing deciding to use it.
It may be it is useful even with only a subset of reviewers
using it. I can't determine this myself, I need feedback from
people who are reviewing regularly.
There's work underway to transfer glibc's trial instance to
sourceware.org, and I've asked for the GDB instance to be
moved at the same time. Apart from anything else, it's probably
easier that way.
> > Let me know what you think!
>
> Thanks for setting this up!
No worries, Siddhesh did all the hard work :D
Cheers,
Gary
--
http://gbenson.net/
next prev parent reply other threads:[~2014-04-17 13:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 10:08 Gary Benson
2014-04-04 22:50 ` Stan Shebs
2014-04-17 18:18 ` Gary Benson [this message]
2014-04-22 15:40 ` Joel Brobecker
2014-04-22 15:51 ` Eric Christopher
2014-04-22 18:37 ` Joel Brobecker
2014-04-24 11:42 ` Siva Chandra
2014-08-02 14:25 ` Mike Frysinger
2014-04-29 17:25 ` Tom Tromey
2014-04-29 17:36 ` Eli Zaretskii
2014-04-29 18:58 ` Joel Brobecker
2014-04-30 9:19 ` Gary Benson
2014-04-30 12:45 ` Joel Brobecker
2014-04-29 19:33 ` Pedro Alves
2014-04-29 22:32 ` Breazeal, Don
2014-04-30 1:08 ` Pedro Alves
2014-04-30 3:45 ` Breazeal, Don
2014-05-21 14:47 ` Tom Tromey
2014-05-21 17:18 ` Pedro Alves
2014-05-21 17:49 ` Joel Brobecker
2014-05-21 18:03 ` Eli Zaretskii
2014-05-21 18:23 ` Joel Brobecker
2014-05-21 18:48 ` Eli Zaretskii
2014-05-21 19:45 ` Joel Brobecker
2014-05-21 21:35 ` Pedro Alves
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=20140417135040.GA891@blade.nx \
--to=gbenson@redhat.com \
--cc=gdb@sourceware.org \
--cc=stanshebs@earthlink.net \
/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