lkml.org 
[lkml]   [1999]   [Feb]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    SubjectRe: Kernel interface changes (was Re: cdrecord problems on
    Date
    >This thread isn't about going from 2.0 to 2.2; it's about going from
    >2.0.33 to 2.0.34. In the past, changes such as this caused major
    >compatibility headaches; this must be prevented from happening in the
    >future if Linux expects to get anywhere.

    Or other subminor releases. I never said that needed changes at major
    release boundaries were unreasonable (in this case, I was informed
    that the change was 2.2.0->2.2.1. It appears the report I got was
    erroneous). Steven, please read the original arguments before getting
    so far off track (And note that Alan gave a definitive answer to those
    arguments that I was satisfied with, assuming kernel/dist developers
    could pull it off in reality). And despite Derek generally agreeing
    with me, he applied my argument far beyond what I intended to address.

    >> And anyway, this isn't linux-scsi related...
    >
    >Actually, this whole thread started because one developer I know kept
    >getting the SCSI interface changed out from under him, again, *in* *a*
    >*stable* *release*; therefore, it is certainly linux-scsi related.

    Not SCSI specifically, but kernel interfaces in general.

    My original argument used SCSI SG as an (immediate) example. It was
    in no way specific only to SCSI and now the argument has nothing to do
    with SCSI. We should stop Cc:ing the SCSI/cdwrite lists.

    Monty

    -
    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.tux.org/lkml/

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