linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Ted Ts'o" <tytso@mit.edu>, Elvis Dowson <elvis.dowson@mac.com>,
	Janakiram Sistla <janakiram.sistla@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Forked android kernel development from linux kernel mainline
Date: Sat, 6 Nov 2010 16:09:44 -0700	[thread overview]
Message-ID: <20101106230944.GA8985@kroah.com> (raw)
In-Reply-To: <20101106192259.GB2935@thunk.org>

On Sat, Nov 06, 2010 at 03:22:59PM -0400, Ted Ts'o wrote:
> Given that the Android kernel developers have already spent upwards of
> ten times the amount of engineering hours it would take forward port
> their kernel patches to each upstream kernel version for the next
> several years, finding a path that meets their requirements as well as
> those of the upstream kernel maintainers may not be a trivial thing.
> 
> Also keep in mind that someone no less than Linus Torvalds has said
> that sometimes forks are good, and that the _freedom_ to fork is
> critical.  But if anyone feels that figuring out some way to make the
> android kernel patches (a) upstreamable, and (b) compatible with
> android's userspace is their itch to scratch, the other part of the
> open source ethos is that they are certainly free to try.

As per the Rusty Russell rule of lkml etiquette, we are all allowed to
participate, or start, one massive, no-holds-barred, ugly as mud flame
war per year.  Remembering that the year was going to be over soon and I
didn't think I had met my quota for this yet, I started to respond to
this email.

But after composing it, I realized that it was not going to change
anyone's feelings about the manner, nor cause anything constructive to
ever occur, besides giving zillions of electrons something to do
lighting up /. comment threads.  So I've deleted it, and will just
respond with this simple line:

  I respectively disagree with your opinion, so we will have to just
  agree to disagree at the moment.

The carrots need to be pulled from the garden now, before the next rain
sets in up here in the Pacific northwest, turning them into orange and
purple mush, so I'll go do that, getting my hands dirty with real dirt,
instead of wearing out my fingertips in creating virtual mud here.

cordially,

greg k-h

  parent reply	other threads:[~2010-11-06 23:12 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-30 18:18 Forked android kernel development from linux kernel mainline Elvis Dowson
2010-11-02 21:25 ` Janakiram Sistla
2010-11-06 18:12   ` Greg KH
2010-11-06 19:22     ` Ted Ts'o
2010-11-06 19:40       ` Anca Emanuel
2010-11-06 23:40         ` Ted Ts'o
2010-11-06 23:52           ` david
2010-11-07  0:03             ` Ted Ts'o
2010-11-07  0:13               ` Alan Cox
2010-11-07  0:20                 ` Janakiram Sistla
2010-11-09 16:30                 ` Mark Brown
2010-11-07  0:20               ` david
2010-11-10 13:54               ` Pavel Machek
2010-11-10 20:38                 ` Rafael J. Wysocki
2011-01-11 14:33                   ` Pavel Machek
2010-11-06 23:42         ` Janakiram Sistla
2010-11-06 23:09       ` Greg KH [this message]
2010-11-07  0:24         ` Randy Dunlap
2010-11-07  8:38     ` Elvis Dowson
2010-11-07 11:44       ` Anca Emanuel
2010-11-07 15:57         ` Greg KH
2010-11-07 20:06           ` Elvis Dowson
2010-11-07 21:31             ` Greg KH
2010-11-07 21:46               ` Arnaud Lacombe
2010-11-07 21:47                 ` Arnaud Lacombe
2010-11-09 18:10             ` Elvis Dowson
2010-11-09 18:24               ` Greg KH
2010-11-09 18:37                 ` Elvis Dowson
2010-11-09 18:42                   ` david
2010-11-09 18:52                     ` Elvis Dowson
2010-11-09 20:55                       ` Ted Ts'o
2010-11-09 22:32                         ` Alan Cox
2010-11-10  0:35                           ` Ted Ts'o
2010-11-10  9:53                             ` Florian Mickler
2010-11-10 20:55                             ` Alan Cox
2010-11-07 21:44           ` Arnaud Lacombe
2010-11-07 21:59             ` Greg KH
2010-11-07 23:09               ` Arnaud Lacombe
2010-11-08  1:42                 ` Greg KH
2010-11-08  2:22                   ` Arnaud Lacombe
2010-11-09 13:27                 ` Florian Fainelli
2010-11-11  0:33               ` Roland Dreier
2010-11-11  0:40                 ` Thomas Gleixner
2010-11-12  3:15                   ` Roland Dreier
2010-11-12 10:26                     ` Florian Fainelli
2010-11-11  0:47                 ` Greg KH
2010-11-11 11:21                   ` Florian Fainelli
2010-11-12  3:17                     ` Roland Dreier
2010-11-11 11:18                 ` Florian Fainelli
2010-11-09 13:27             ` Florian Fainelli
2010-11-09 13:51               ` [OpenWrt-Devel] " Wolfgang Spraul
2010-11-13  3:06             ` Arnaud Lacombe
2010-11-15 17:34             ` Stefan Monnier
2010-11-16  6:23               ` Brian Swetland
2010-11-16  7:02                 ` Anca Emanuel

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=20101106230944.GA8985@kroah.com \
    --to=greg@kroah.com \
    --cc=elvis.dowson@mac.com \
    --cc=janakiram.sistla@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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;
as well as URLs for NNTP newsgroup(s).