From: Eric Christopher <echristo@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Gary Benson <gbenson@redhat.com>,
Stan Shebs <stanshebs@earthlink.net>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Patchwork patch tracking system
Date: Tue, 22 Apr 2014 15:51:00 -0000 [thread overview]
Message-ID: <CALehDX6F9wMzSMF2iA-UdGnOTSxpj6uywbad84Uy=HmBnu88Gw@mail.gmail.com> (raw)
In-Reply-To: <20140422130652.GG5790@adacore.com>
On Tue, Apr 22, 2014 at 6:06 AM, Joel Brobecker <brobecker@adacore.com> wrote:
>> > 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.
>
> In my opinion, the GDB project is in dire need of a way to track
> patches. Using one's mailbox to track patches just does not work.
> But I think that we would need full commitment to the tool from
> the project, or else it'd quickly start overflowing with stale
> info.
>
> There is a tool that we use internally at AdaCore which I was starting
> to think of proposing for GDB, called geritt. From what I have been
> able to see from patchwork's webpage, geritt seems like a much more
> advanced system compared to patchwork. But the tradeoff is that using
> geritt requires a bit more work as well, and that part or all of
> the review process would happen on geritt, rather than the mailing-list.
> It's not very intuitive at first, but it is very easy and lightweight.
>
> I personally believe geritt's approach to be better in the long run.
> But, while I am worried about having communication and patch handling
> be done via two distinct systems, patchwork's simpler approach might be
> working well enough without requiring the big shift in patch-reviewing
> paradigm.
>
FWIW we (some of the google folk) looked at geritt for LLVM and
discarded in favor of phabricator. It seemed to solve a lot of the
problems that we had and allowed communication to and from the mailing
lists for patches which was key for us as we have a similar review
style to gcc/gdb/binutils. We didn't want to remove the ability for
people to send patches to the mailing lists, but yet get a better
review mechanism for large patches/queuing/etc.
Just piping in since we recently did some of this work. Feel free to
let me know if you have any questions on our experiences.
-eric
next prev parent reply other threads:[~2014-04-22 15:40 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
2014-04-22 15:40 ` Joel Brobecker
2014-04-22 15:51 ` Eric Christopher [this message]
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='CALehDX6F9wMzSMF2iA-UdGnOTSxpj6uywbad84Uy=HmBnu88Gw@mail.gmail.com' \
--to=echristo@gmail.com \
--cc=brobecker@adacore.com \
--cc=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