public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* The difference between Linus's kernel and Alan Cox's kernel
  2001-05-25 19:51 ` Jeff Garzik
@ 2001-05-25 20:12   ` Thiago Vinhas de Moraes
  2001-05-25 21:32     ` Erik Mouw
  2001-05-25 23:05     ` Alan Cox
  0 siblings, 2 replies; 7+ messages in thread
From: Thiago Vinhas de Moraes @ 2001-05-25 20:12 UTC (permalink / raw)
  To: linux-kernel, Linus Torvalds, Alan Cox

-----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-----

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: The difference between Linus's kernel and Alan Cox's kernel
@ 2001-05-25 21:17 Wayne.Brown
  0 siblings, 0 replies; 7+ messages in thread
From: Wayne.Brown @ 2001-05-25 21:17 UTC (permalink / raw)
  To: Thiago Vinhas de Moraes; +Cc: linux-kernel, Linus Torvalds, Alan Cox



It really ought to be Linus and/or Alan who answers this, but from my own
observations, here's the way I think it goes:

Alan and Linus don't always agree on what should be in the kernel; and even when
they do, they sometimes disagree on when something is ready to be included.
Alan may think a particular set of patches are ready, while Linus thinks they
need to mature a bit more; or perhaps he thinks the whole approach is wrong and
should be scrapped.  So Alan puts it in his kernel, and Linus leaves it out of
his.  (Of course, sometimes it's Linus who adds something that Alan rejects.)
It sometimes happens that one of these new ideas turns out better than expected
(especially after going through a few bug report/new patch cycles), and the
person who rejected it changes his mind and includes it later; or maybe it
doesn't work out and gets dropped altogether.  Also, as you've already observed,
Alan regularly resyncs major parts of his tree with Linus' so they don't get too
far apart, and Linus occasionally does the same.

It used to bother me, too, to have to keep up with two different kernel trees.
But I've come to realize that this is a Good Thing.  It provides a way for
people with different viewpoints to approach an idea from more than one
direction.  If the two kernels are trying to solve a particular problem in
different ways, we get to see how each approach works in the real world, rather
than just in a theoretical discussion.  If the two kernels branch too far apart
it could be a problem, but Linus and Alan have been diligent about keeping that
from happening.  I think the interplay (is "competition" too strong a word?)
between the two branches has helped make the "official" kernel better than it
might have been otherwise.

Wayne



^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: The difference between Linus's kernel and Alan Cox's kernel
  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 23:05     ` Alan Cox
  1 sibling, 1 reply; 7+ messages in thread
From: Erik Mouw @ 2001-05-25 21:32 UTC (permalink / raw)
  To: Thiago Vinhas de Moraes; +Cc: linux-kernel, Linus Torvalds, Alan Cox

On Fri, May 25, 2001 at 05:12:39PM -0300, Thiago Vinhas de Moraes wrote:
> 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.

I just added this to the kernelnewbies FAQ:

  http://www.kernelnewbies.org/faq.php3


Erik

-- 
J.A.K. (Erik) Mouw, Information and Communication Theory Group, Department
of Electrical Engineering, Faculty of Information Technology and Systems,
Delft University of Technology, PO BOX 5031,  2600 GA Delft, The Netherlands
Phone: +31-15-2783635  Fax: +31-15-2781843  Email: J.A.K.Mouw@its.tudelft.nl
WWW: http://www-ict.its.tudelft.nl/~erik/

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: The difference between Linus's kernel and Alan Cox's kernel
  2001-05-25 21:32     ` Erik Mouw
@ 2001-05-25 21:40       ` CaT
  2001-05-25 21:50         ` Erik Mouw
  0 siblings, 1 reply; 7+ messages in thread
From: CaT @ 2001-05-25 21:40 UTC (permalink / raw)
  To: Erik Mouw; +Cc: Thiago Vinhas de Moraes, linux-kernel, Linus Torvalds, Alan Cox

On Fri, May 25, 2001 at 11:32:18PM +0200, Erik Mouw wrote:
> On Fri, May 25, 2001 at 05:12:39PM -0300, Thiago Vinhas de Moraes wrote:
> > 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.
> 
> I just added this to the kernelnewbies FAQ:
> 
>   http://www.kernelnewbies.org/faq.php3

Typo: First para, last sentence: s/Linux/Linus/

-- 
CaT (cat@zip.com.au)		*** Jenna has joined the channel.
				<cat> speaking of mental giants..
				<Jenna> me, a giant, bullshit
				<Jenna> And i'm not mental
					- An IRC session, 20/12/2000


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: The difference between Linus's kernel and Alan Cox's kernel
  2001-05-25 21:40       ` CaT
@ 2001-05-25 21:50         ` Erik Mouw
  0 siblings, 0 replies; 7+ messages in thread
From: Erik Mouw @ 2001-05-25 21:50 UTC (permalink / raw)
  To: CaT; +Cc: Thiago Vinhas de Moraes, linux-kernel, Linus Torvalds, Alan Cox

On Sat, May 26, 2001 at 07:40:18AM +1000, CaT wrote:
> On Fri, May 25, 2001 at 11:32:18PM +0200, Erik Mouw wrote:
> > I just added this to the kernelnewbies FAQ:
> > 
> >   http://www.kernelnewbies.org/faq.php3
> 
> Typo: First para, last sentence: s/Linux/Linus/

Oops. Fixed, thanks.


Erik

-- 
J.A.K. (Erik) Mouw, Information and Communication Theory Group, Department
of Electrical Engineering, Faculty of Information Technology and Systems,
Delft University of Technology, PO BOX 5031,  2600 GA Delft, The Netherlands
Phone: +31-15-2783635  Fax: +31-15-2781843  Email: J.A.K.Mouw@its.tudelft.nl
WWW: http://www-ict.its.tudelft.nl/~erik/

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: The difference between Linus's kernel and Alan Cox's kernel
  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 23:05     ` Alan Cox
  2001-05-28 15:50       ` Thiago Vinhas de Moraes
  1 sibling, 1 reply; 7+ messages in thread
From: Alan Cox @ 2001-05-25 23:05 UTC (permalink / raw)
  To: Thiago Vinhas de Moraes; +Cc: linux-kernel, Linus Torvalds, Alan Cox

> 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.


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: The difference between Linus's kernel and Alan Cox's kernel
  2001-05-25 23:05     ` Alan Cox
@ 2001-05-28 15:50       ` Thiago Vinhas de Moraes
  0 siblings, 0 replies; 7+ messages in thread
From: Thiago Vinhas de Moraes @ 2001-05-28 15:50 UTC (permalink / raw)
  To: Alan Cox, Thiago Vinhas de Moraes; +Cc: linux-kernel, Linus Torvalds, Alan Cox

Em Sex 25 Mai 2001 20:05, Alan Cox escreveu:
> > 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.

But will this happen forever? You (Alan) is currently the maintaner of the 
2.2 tree. Won't you be going to assume the 2.4 tree, while the 2.5 series 
development starts?

BTW, Thanks for your answer.

Regards,
-- 
________________________________
 Thiago Vinhas de Moraes
 NetWorx - A SuaCompanhia.com

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2001-05-28 16:06 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-05-25 21:17 The difference between Linus's kernel and Alan Cox's kernel Wayne.Brown
  -- strict thread matches above, loose matches on Subject: below --
2001-05-25 19:37 ac15 and 2.4.5-pre6, pwc format conversion 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
2001-05-28 15:50       ` Thiago Vinhas de Moraes

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox