From: "Scott Preece" <sepreece@gmail.com>
To: "Jeff Garzik" <jeff@garzik.org>
Cc: "Alan Cox" <alan@lxorguk.ukuu.org.uk>,
"Chris Malton" <chrism@cjsoftuk.dyndns.org>,
linux-kernel@vger.kernel.org
Subject: Re: [Fwd: Re: Google are using linux kernel - what do you know about the source?]
Date: Wed, 23 May 2007 19:16:35 -0700 [thread overview]
Message-ID: <7b69d1470705231916q5bfd9c0bo36021f823729b8a3@mail.gmail.com> (raw)
In-Reply-To: <46549F45.4040403@garzik.org>
On 5/23/07, Jeff Garzik <jeff@garzik.org> wrote:
> Alan Cox wrote:
> >> Google does not distribute their software, so they do not have to make
> >> their modifications public.
> >
> > They do for the kernel - they produce an "appliance".
>
> Ah, I stand corrected.
>
>
> >> WRT the Linux kernel, Google is essentially a closed source company.
> >
> > They've quietly fed little bits back now and then but not made a big song
> > and dance about it. Hopefully with Andrew there and the like more will
> > occur.
>
> Strange that the NIC and SATA driver bits never seem to be among those
> "little bits"... Along with filesystem and other modifications
> discussed in the press, or observable net stack behavior when connecting
> to their computers over the 'net.
>
> So, emphasis on "little", I guess.
>
> Jeff
---
For 2.6.21, Jon Corbet's count for LWN showed Google ninth on the list
(by number of changesets), among companies whose contributors could be
identified.
prev parent reply other threads:[~2007-05-24 2:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 16:58 Chris Malton
2007-05-23 19:31 ` Jeff Garzik
2007-05-23 20:02 ` Alan Cox
2007-05-23 20:08 ` Jeff Garzik
2007-05-23 21:59 ` Francois Romieu
2007-05-24 2:16 ` Scott Preece [this message]
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=7b69d1470705231916q5bfd9c0bo36021f823729b8a3@mail.gmail.com \
--to=sepreece@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=chrism@cjsoftuk.dyndns.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.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®