From: "Cédric Augonnet" <cedric.augonnet@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Linux Kernel Story
Date: Thu, 12 Jul 2007 11:02:09 -0400 [thread overview]
Message-ID: <f56c1ba00707120802g1e9032f9l96efd1a3b4a1f71a@mail.gmail.com> (raw)
In-Reply-To: <20070712143929.GA8147@localhost.localdomain>
2007/7/12, thinkinnight@gmail.com <thinkinnight@gmail.com>:
> On Thu, Jul 12, 2007 at 11:08:52AM -0300, Renato S. Yamane wrote:
> > Vijayakumar Subburaj escreveu:
> > >My first mail to lkml.
> >
> > Welcome :-)
> >
> > >I would like to know what happened to linux kernel from its 1.0.
> >
> > From 1.0 to 2.6.22.1?
> > Wowwwwwwwwwww
> >
> > I think that you can read all changelogs available in www.kernel.org. In
> > 2 years you finish read 2.4 and 2.6 series :-)
> >
> > Are you try <http://kernelnewbies.org/LinuxChanges>?
> >
> I think this is a good idea to know all the changes!
>
> > Regards,
> > Renato
> > -
If you have to study some given sub-system, why not, you might have to
look at how this evolved from years to years, that must already be a
huge work from 2.0 to now for any single part of the kernel.
But seriously, if it's already virtually impossible to get a real
picture of the overall kernels, trying to figure out all changes from
1.0 to now, for all subsystems sounds a little illusory. Moreover they
might have just been all rewritten several times since.
But perhaps what Vijayakumar was looking for is more the different
feature that were added within the curse of years (eg : SMP) ?
Regards,
Cédric
next prev parent reply other threads:[~2007-07-12 15:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 13:27 Vijayakumar Subburaj
2007-07-12 14:08 ` Renato S. Yamane
2007-07-12 14:39 ` thinkinnight
2007-07-12 15:02 ` Cédric Augonnet [this message]
2007-07-12 16:40 ` Lennart Sorensen
2007-07-12 18:24 ` Ruben Junkie
2007-07-13 9:59 ` Tilman Schmidt
2007-07-13 11:02 ` Wander Winkelhorst
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=f56c1ba00707120802g1e9032f9l96efd1a3b4a1f71a@mail.gmail.com \
--to=cedric.augonnet@gmail.com \
--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®