Linux-kernel mailing list archive 1998-25,: Re: Weird spelling fixes in 2.1.107

# Re: Weird spelling fixes in 2.1.107

Jon Hamilton (hamilton@pobox.com)
Fri, 26 Jun 1998 19:47:48 -0500

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Aaron Ray: "Shift + pg up & pg down"
- Previous message: Alan Cox: "Re: 2.1.107 + fb + s3virge = FAIL"
- Maybe in reply to: Martin Mares: "Weird spelling fixes in 2.1.107"
- Next in thread: Michael Elizabeth Chastain: "Re: Weird spelling fixes in 2.1.107"

In message <Pine.LNX.3.91.980626153836.7044C-100000@mhw.OIT.IUPUI.EDU>, "Mark H
. Wood" wrote:
} On Fri, 26 Jun 1998, Tethys wrote:
} [deletia]
} > >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.
}
} I have *some* sympathy because there are *two* problems here:
}
} 1. Someone who is trying out an OS for the first time should not be
} using an experimental kernel, true. HOWEVER:
}
} 2. Public interfaces shouldn't be incompatibly changed without a good
} reason and plenty of warning.

I don't think this argument holds water. How much warning do you get
when Linus makes a change in a development kernel? If you're lucky, it'll
get mentioned in the release announcement; often it doesn't get any public
mention until somebody notices that it's changed.

    --
       Jon Hamilton
       hamilton@pobox.com

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.rutgers.edu

- Next message: Aaron Ray: "Shift + pg up & pg down"
- Previous message: Alan Cox: "Re: 2.1.107 + fb + s3virge = FAIL"
- Maybe in reply to: Martin Mares: "Weird spelling fixes in 2.1.107"
- Next in thread: Michael Elizabeth Chastain: "Re: Weird spelling fixes in 2.1.107"