From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Grozdan Nikolov" <microchip@chello.be>
Cc: "jimmy bahuleyan" <knight.camelot@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: How innovative is Linux?
Date: Sun, 24 Jun 2007 01:15:34 +0200 [thread overview]
Message-ID: <9a8748490706231615t7ccd9467wa79fe98d5f783ec3@mail.gmail.com> (raw)
In-Reply-To: <200706232106.11656.microchip@chello.be>
On 23/06/07, Grozdan Nikolov <microchip@chello.be> wrote:
> On Saturday 23 June 2007 20:54, jimmy bahuleyan wrote:
[snip]
> > I'm not a kernel developer myself, but i think there are lots of
> > resources on the internet where you can read watered down versions of
> > discussions happening on this list.
>
> If there are I'm unaware of those, thanks for the hint though
>
A few places:
The LinuxChanges page at kernelnewbies: http://kernelnewbies.org/LinuxChanges
The kernel section of LWN: http://lwn.net/Kernel/
Kerneltrap: http://kerneltrap.org/
Kernel Traffic (unfortunately no longer updated): http://kerneltraffic.org/
And then you have list archives like :
http://lkml.org/
http://marc.info/?l=linux-kernel
http://www.uwsg.iu.edu/hypermail/linux/kernel/index.html
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2007-06-23 23:15 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-23 12:17 Grozdan Nikolov
2007-06-23 14:43 ` Alan Cox
2007-06-23 15:22 ` Grozdan Nikolov
2007-06-23 15:46 ` Alan Cox
2007-06-23 16:12 ` Torsten Duwe
2007-06-23 16:19 ` Grozdan Nikolov
2007-06-23 16:42 ` Torsten Duwe
2007-06-23 16:54 ` Matthew Jacob
2007-06-23 17:30 ` jimmy bahuleyan
2007-06-23 17:49 ` Diego Calleja
2007-06-23 19:23 ` Alan Cox
2007-06-23 21:02 ` Al Viro
2007-06-23 22:13 ` Alan Cox
2007-06-23 18:12 ` Jan Engelhardt
2007-06-23 19:44 ` Alan Cox
2007-06-23 17:38 ` Benny Amorsen
2007-06-23 19:18 ` Jeffrey V. Merkey
2007-06-23 18:36 ` Grozdan Nikolov
2007-06-24 4:31 ` Rik van Riel
2007-06-23 22:02 ` Carlo Wood
2007-06-23 22:16 ` David Kane
[not found] ` <345c044f0706231513u46d870es6539bdf5797b305b@mail.gmail.com>
2007-06-23 22:27 ` Alan Cox
2007-06-25 9:39 ` Hiro Yoshioka
2007-06-25 22:57 ` Adrian Bunk
2007-06-24 21:36 ` Nikita Danilov
2007-06-23 18:02 ` Satyam Sharma
2007-06-23 18:17 ` Grozdan Nikolov
2007-06-23 17:53 ` Bernd Petrovitsch
2007-06-23 18:15 ` Grozdan Nikolov
2007-06-23 18:54 ` jimmy bahuleyan
2007-06-23 19:06 ` Grozdan Nikolov
2007-06-23 23:15 ` Jesper Juhl [this message]
2007-06-25 15:12 ` Lennart Sorensen
2007-06-25 15:15 ` Jan Engelhardt
2007-06-25 16:37 ` Randy Dunlap
2007-06-25 16:42 ` Jan Engelhardt
2007-06-25 17:51 ` jimmy bahuleyan
2007-06-26 12:26 ` Helge Hafting
2007-06-23 17:43 Al Boldi
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=9a8748490706231615t7ccd9467wa79fe98d5f783ec3@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=knight.camelot@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=microchip@chello.be \
/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®