From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: tvinhas@networx.com.br (Thiago Vinhas de Moraes)
Cc: linux-kernel@vger.kernel.org,
torvalds@transmeta.com (Linus Torvalds),
alan@lxorguk.ukuu.org.uk (Alan Cox)
Subject: Re: The difference between Linus's kernel and Alan Cox's kernel
Date: Sat, 26 May 2001 00:05:39 +0100 (BST) [thread overview]
Message-ID: <E153QeK-0007Cs-00@the-village.bc.nu> (raw)
In-Reply-To: <01052517123904.01385@zeus.networx.com.br> from "Thiago Vinhas de Moraes" at May 25, 2001 05:12:39 PM
> Why there are two different kernel trees? There is always the official
> release, provided by Torvalds, and then Alan provides a patch merging Linus's
> stuff, and adding (?) tons of bug fixes.
Well it started by accident but it turns out good to have a tree that changes
are merged into, tested by those who need the fixes and reviewed by third
parties before they go to Linus.
So the -ac tree is kind of a peer review, testing and distillation process for
patches.
next prev parent reply other threads:[~2001-05-25 23:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-25 6:50 ac15 and 2.4.5-pre6, pwc format conversion Norbert Preining
2001-05-25 8:48 ` Nemosoft Unv.
2001-05-25 11:15 ` Erik Mouw
2001-05-25 13:22 ` Nemosoft Unv.
2001-05-25 15:58 ` Alan Cox
2001-05-25 19:37 ` Nemosoft Unv.
2001-05-25 19:51 ` Jeff Garzik
2001-05-25 20:12 ` The difference between Linus's kernel and Alan Cox's kernel Thiago Vinhas de Moraes
2001-05-25 21:32 ` Erik Mouw
2001-05-25 21:40 ` CaT
2001-05-25 21:50 ` Erik Mouw
2001-05-25 23:05 ` Alan Cox [this message]
2001-05-28 15:50 ` Thiago Vinhas de Moraes
2001-05-25 23:03 ` ac15 and 2.4.5-pre6, pwc format conversion Alan Cox
2001-05-25 16:52 ` Erik Mouw
2001-05-25 11:00 ` Alan Cox
2001-05-25 21:17 The difference between Linus's kernel and Alan Cox's kernel Wayne.Brown
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=E153QeK-0007Cs-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=tvinhas@networx.com.br \
/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®