I am sorry but the evidence proves otherwise.
Someone has taken it upon themself to be the Spelling and Grammar
Checker
and make capricious changes with total disregard for the impact of those
changes.
>
> What on *earth* are you thinking, giving them the latest development
> kernel? That's what stable kernels are for. Development kernels are by
> nature unstable and liable to break things -- if you really *need* a
> feature in the later 2.1 kernels, decide on a version that supports what
> you need, and *test* it thoroughly. When you're happy that it works,
> send it out to your clients.
As stated in previous e-mail, the clients are either working on porting
internal legacy applications to Linux or writing new applications and
have the desire to work with the development kernel so that when the
development kernel, Lord willing, becomes Linux 2.2 they are prepared.
It is their decision to make and it is also their decision to question
the motives of, in their opinion, a totally capricious act with no
technological merit.
>
> If you need features in 2.1.107 that weren't in earlier versions, then I
> think you need to say that Linux isn't yet ready for your customers, and
> let them use something else until those features are stable under Linux.
>
> >To break code because someone did not like the way cpu & fpu were
> >capitalized is lunacy.
>
> No, to give clients an untested development kernel that's only been out
> for a few days is lunacy, and I'm afraid I have little sympathy for you.
Perhaps you could enlighten me concerning your above statement. How am I
to prohibit a client any client from downloading the developement kernel
from http://www.kernel.org? Perhaps I should send Linus a list of
clients
and their IP addresses so that he can block them from viewing any
http://www.kernel.org Web Pages and strictly prohibit them from
downloading
any development kernels. Of course this would also have to be put in
place
for each mirror of http://www.kernel.org.
>
> Tet
>
> PS. Aside from anything else, this episode show the folly of parsing
> text from /proc -- a programatic interface to get kernel information
> would have been unaffected by this, as well as being more efficient.
> Just my usual uninformed opinion... :-)
To quote David S. Miller
<Begin Quote>
But you did, because now as I read those "new and improved" versions
of the comments I feel like I'm reading a textbook which is dead and
without life, not a piece of source code which is full of life and
personality.
Later,
David S. Miller
davem@dm.cobaltmicro.com
<End Quote>
>
> --
> tethys@ml.com
-- Terry L. Ridder Blue Danube Software (Blaue Donau Software) "We do not write software, we compose it."When the toast is burnt and all the milk has turned and Captain Crunch is waving farewell when the Big One finds you may this song remind you that they don't serve breakfast in hell ==Breakfast==Newsboys
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu