From: Brian Swetland <swetland@google.com>
To: Shawn Pearce <sop@google.com>
Cc: Pavel Machek <pavel@ucw.cz>,
Stefan Schmidt <stefan@datenfreihafen.org>,
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>, Chris Dibona <cdibona@google.com>,
Daniel Berlin <dannyb@google.com>
Subject: Re: Gerrit (was Re: HTC Dream aka. t-mobile g1 support)
Date: Fri, 12 Jun 2009 15:42:21 -0700 [thread overview]
Message-ID: <a55d774e0906121542g182d4814udd66c2d1ebf57cf5@mail.gmail.com> (raw)
In-Reply-To: <1cc472780906121538h5b70fa4dg891ff729fda1a566@mail.gmail.com>
On Fri, Jun 12, 2009 at 3:38 PM, Shawn Pearce<sop@google.com> wrote:
> On Fri, Jun 12, 2009 at 15:22, Pavel Machek <pavel@ucw.cz> wrote:
>> On Fri 2009-06-12 14:50:21, Brian Swetland wrote:
>> > Gerrit is a git patch review system that we (Google/Android) use for
>>
>> Unfortunately, it seems quite unsuitable for kernel.
>>
>> Do I understand it right that to submit kernel patches I'd have to
>> agree to "contributors agreement", and give up my copyright? No,
>> sorry, I don't think I want to do that.
>
> No. The contributor agreement used by review.source.android.com is a stronger version of the Developers Certificate of Origin normally used by kernel
> contributors.
> For the actual agreement text see[1], but the basic principle is the same.
> No assignment of copyright, only assignment of license for redistribution,
> which is what the GPL asks anyway. It also contains a patent provision,
> similar to what the Apache License contains, to protect the project leads
> from submarine patent infringement by code contributed by a patent holder.
> [1] https://review.source.android.com/static/cla_individual.html
When we first discussed the CLA, I raised this concern (that the
mainline kernel folks would not be thrilled by another system in
addition to Signed-off-by), and was informed that we should not have
to require CLA acceptance for contributions to the kernel/... trees.
I'm not sure if Gerrit is setup to handle this yet.
We will always happily accept kernel patches via email/mailinglist,
per the standard linux kernel development model.
Brian
next prev parent reply other threads:[~2009-06-12 22:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 21:50 Brian Swetland
2009-06-12 22:22 ` Pavel Machek
[not found] ` <1cc472780906121538h5b70fa4dg891ff729fda1a566@mail.gmail.com>
2009-06-12 22:42 ` Brian Swetland [this message]
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=a55d774e0906121542g182d4814udd66c2d1ebf57cf5@mail.gmail.com \
--to=swetland@google.com \
--cc=cdibona@google.com \
--cc=dannyb@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®