public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: "Giorgio A." <jh@libero.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Need info on kernel philosofy
Date: Wed, 14 Nov 2001 13:49:25 -0800	[thread overview]
Message-ID: <20011114134925.A23386@mikef-linux.matchmail.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0111141212220.24024-100000@anime.net> <00a001c16d4b$7dabf240$0400a8c0@jh>
In-Reply-To: <00a001c16d4b$7dabf240$0400a8c0@jh>

On Wed, Nov 14, 2001 at 09:32:34PM +0100, Giorgio A. wrote:
> hi all,
> i know this is gonna be the lamest question of the year, but i didn't found
> a valid answer elsewhere !
> I'm using linux as a sysadmin since slack 3.1, and i've subscribed to this

I started back when 2.0.35 was the latest stable.  I think slack was 3.5
then...

> list about 2 month ago. I'm not a developer, i don't have the knowledge, but
> i like to watch at all of your e-mails since it makes me feel like i'm
> really following the growing of the penguin !

Yep.  You can be very helpful with testing of patches, and documentation
patches...

>Only now i discovered that
> there're 2 trees, the Alans' and the Linus' (here in alphabetical order :-),
> and in these days i saw Linus saying that 2.4.15 is ready to be the result
> of a merge between the two trees. 

Not really.  Alan has been handling the "almost ready for merging" patches
for a while now.  Linus has particular requirements for the patches he
accepts, and Alan helps feed Linus patches the way he likes them.

This has been going on for several years now.

>Now, i wonder if merging the 2 trees is an
> usual thing, so it would be happened also with 2.2 and 2.0 (thing that i
> can't knew, since at that time i wasn't subscribed to LKML), or if i'm
> taking part of a kind of an historycal event, i.e. the fusion of the 2
> kernel trees.

Don't know when 2.2 was placed in Alan's hands.  Know even less about 2.0...

Mike

  reply	other threads:[~2001-11-14 21:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-14 18:04 [lm_sensors] hard lockup on modprobe w83781d with Tyan Dual K7/Thunder Hans-Peter Jansen
2001-11-14 20:13 ` Dan Hollis
2001-11-14 20:32   ` Need info on kernel philosofy Giorgio A.
2001-11-14 21:49     ` Mike Fedyk [this message]
2001-11-14 21:52 ` [lm_sensors] hard lockup on modprobe w83781d with Tyan Dual K7/Thunder Hans-Peter Jansen
2001-11-15  2:50   ` Dan Hollis
2001-11-15 15:06     ` [lm_sensors] wrong sensors readings from w83782d on " Hans-Peter Jansen
2001-11-15 19:25       ` Dan Hollis
  -- strict thread matches above, loose matches on Subject: below --
2001-11-14 22:32 Need info on kernel philosofy Mario Vanoni

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=20011114134925.A23386@mikef-linux.matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=jh@libero.it \
    --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