From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] Gerrit for BR
Date: Fri, 21 Oct 2011 08:57:14 +0200 [thread overview]
Message-ID: <20111021085714.2e661569@skate> (raw)
In-Reply-To: <4EA02C2A.6070405@visionsystems.de>
Le Thu, 20 Oct 2011 16:11:54 +0200,
Yegor Yefremov <yegor_sub1@visionsystems.de> a ?crit :
> What do you think about using Gerrit (http://code.google.com/p/gerrit/) for Buildroot? Many OSS projects seem to switch to this system.
How does it compare to patchwork (http://patchwork.ozlabs.org/) ?
Patchwork works in relation to a mailing-list, from which it
automatically picks up patches and related review comments, and it
allows maintainers to track which patches have been applied/not applied.
How does Gerrit work in that respect?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-10-21 6:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-20 14:11 [Buildroot] [RFC] Gerrit for BR Yegor Yefremov
2011-10-20 15:44 ` C.A, Subramaniam
2011-10-21 6:57 ` Thomas Petazzoni [this message]
2011-10-21 7:38 ` Bryan Hundven
2011-10-21 7:43 ` Bryan Hundven
2011-10-21 7:49 ` Peter Korsgaard
2011-10-21 10:17 ` Yegor Yefremov
2011-10-21 11:19 ` Thomas De Schampheleire
2011-10-21 11:48 ` Thomas Petazzoni
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=20111021085714.2e661569@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.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