> And I think this is great. It's a seperate kernel patch which serves
> the needs of some people very well.
But the fact that it's seperate makes it a PITA for mere mortals to keep
up to date kernels. i.e. A new kernel is released and the various patch
sets they use don't apply cleanly. Then they get to do lots of head
scratching and beard pulling while manually fixing rejections, or they get
to wait to upgrade until the maintainer of each patch set releases an
updated version.
> problem extremely well (limited number of scsi/tty/etc. devices). But
> because it was unclean and not really the correct solution to the
> problem, it never went into Linus's tree.
So the question is, should patches that are of value but not "the one true
solution to the problem" be integrated into the mainstream kernel source
and be replaced when something better comes along, or should everyone just
have to wail until a perfect solution is ready?
------------------------------------------------------------------
Jon Lewis <jlewis@fdt.net> | Spammers will be winnuked or
Network Administrator | drawn and quartered...whichever
Florida Digital Turnpike | is more convenient.
______http://inorganic5.fdt.net/~jlewis/pgp for PGP public key____
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html