[lkml]   [1998]   [Oct]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Automating 2.3 patches
Someone said:
"This way, users could determine their own level of
need/risk in testing patches. And, Linus could use
the statistics to determine when to include a patch
in the development kernel (same would be true of the
stable kernel too). Anybody could go the web site
and look at the stats for any patch to determine."

Alan said:
"Then instead of 2 or 3 kernel trees with get N!
limited by the number of Linux users."

"Not good."

Alan, you forgot that Mr. Linus Torvalds will still be the official final
arbitrator, and _his_ kernel will still be the _official_ kernel, regardless of
the 15 gazillion different kernel trees that may exist out there.

Again, in looking at the current setup, not all of us have the exact number of
patches/drivers running in our respective machines anyway, so why worry?

Alan also said:
"If patches didnt interact it would be a wonderful idea,
but they do, frequently in bizarre and horrible ways."

That is why we need people like Linus, you (Mr. Cox) and others to give the rest
of lowly users your authoritative opinions in this Linux-Kernel list.

I'd also like to add the following suggestions:

1. Space for short descriptions of the patches
(much like what's going on in this list)

2. Space for people to post short comments
(much like /.)

3. Links to places where those patches are available, and

4. Simple good / bad voting feature for that particular patch.

In that way, people can read about the good, bad, and the ugliness of any
particular patch before they actually apply on their own machine, and if they
want to try the patches, they can use the links provided and start downloading.

It would be nice if the website is structured in such a way that patches for
memory would be put in the memory section, patches for hardware can be put in
their respective category (such as hardware/scsi).


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:44    [W:0.038 / U:2.216 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site