mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Brian Swetland <swetland@google.com>
To: Stefan Schmidt <stefan@datenfreihafen.org>
Cc: Pavel Machek <pavel@ucw.cz>,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	kernel list <linux-kernel@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.arm.linux.org.uk>,
	Greg KH <greg@kroah.com>,
	sop@google.com
Subject: Gerrit (was Re: HTC Dream aka. t-mobile g1 support)
Date: Fri, 12 Jun 2009 14:50:21 -0700	[thread overview]
Message-ID: <a55d774e0906121450x12bab7b0sc1f4de0115a1af61@mail.gmail.com> (raw)

On Fri, Jun 12, 2009 at 10:35 AM, Stefan
Schmidt<stefan@datenfreihafen.org> wrote:
>> I think the intent is to have a
>> Gerrit instance to accept contributions.  I'll have to look into
>> whether this can be done without signing the agreement.  Right
>> now, I can't even contribute anything, so there are a lot of
>> issues to work out.
>
> Gerrit is the Android review system? I'm only interested into the kernel and
> especially running a mainline kernel on different devices. Anyway, a public
> review process and some more informations on what you are working and how you
> would like to bring it mainline would help here.

Gerrit is a git patch review system that we (Google/Android) use for
android development (kernel and otherwise).  Some other folks like
Qualcomm, and TI (see http://review.omapzoom.org/) have adopted it as
well.  We're still happy to accept patches via email and
review/discuss them on the usual mailing lists as well.  It'd be cool
to get an automated process set up to slurp submitted patches into
Gerrit at some point, and further unify the two different workflows.

Gerrit's very actively maintained by Shawn O. Pearce:
http://code.google.com/p/gerrit/

Here's an example of a patch in Gerrit (though a dull one -- when
logged in you can basically annotate the diff with line by line
comments, etc, which is pretty slick if you like that sort of thing):
https://review.source.android.com/10348

Brian

             reply	other threads:[~2009-06-12 21:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-12 21:50 Brian Swetland [this message]
2009-06-12 22:22 ` Pavel Machek
     [not found]   ` <1cc472780906121538h5b70fa4dg891ff729fda1a566@mail.gmail.com>
2009-06-12 22:42     ` Brian Swetland
2009-06-12 22:43       ` Shawn Pearce
2009-06-12 22:45         ` Brian Swetland
2009-06-12 22:49       ` Pavel Machek
2009-06-12 22:48     ` Pavel Machek

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=a55d774e0906121450x12bab7b0sc1f4de0115a1af61@mail.gmail.com \
    --to=swetland@google.com \
    --cc=greg@kroah.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=pavel@ucw.cz \
    --cc=sop@google.com \
    --cc=stefan@datenfreihafen.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

all inboxes | Powered by JetHome®