From: Thiago Vinhas de Moraes <tvinhas@networx.com.br>
To: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@transmeta.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: The difference between Linus's kernel and Alan Cox's kernel
Date: Fri, 25 May 2001 17:12:39 -0300 [thread overview]
Message-ID: <01052517123904.01385@zeus.networx.com.br> (raw)
In-Reply-To: <XFMail.010525213709.nemosoft@smcc.demon.nl> <3B0EB7A6.E0B17C79@mandrakesoft.com>
In-Reply-To: <3B0EB7A6.E0B17C79@mandrakesoft.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi.
Maybe lots of you already know the answer, maybe it's a really stupid
question. If it is, please tell me. I'll not be offended.
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.
Why aren't the -ac patches completely merged to the official tree, and you
centralize the work on single kernel patches ?? Won't it be easier to
administrate?
I'm so sorry if it's a really stupid question. It's because I never know what
pre-patch to apply, the -ac* or the -pre*. In doubt, I apply Alan's, because
it appears to be always Linus stuff, and more bug fixes, recently, the
Linus's -pre* appears to have merges from the -ac on each release.
I just don't understand why it can all be merged.
Regards,
Thiago Vinhas de Moraes
NetWorx - A SuaCompanhia.com
Rio de Janeiro - Brazil
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE7Dry8GHuTR9LK9ocRAsIIAKCs/uMrlDxZSlst8J0h0D6k6tylkACeKNMB
ESyPHbcpcbxWr48NySQYUBs=
=FotG
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2001-05-25 20:15 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 ` Thiago Vinhas de Moraes [this message]
2001-05-25 21:32 ` The difference between Linus's kernel and Alan Cox's kernel Erik Mouw
2001-05-25 21:40 ` CaT
2001-05-25 21:50 ` Erik Mouw
2001-05-25 23:05 ` Alan Cox
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=01052517123904.01385@zeus.networx.com.br \
--to=tvinhas@networx.com.br \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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®