>Dont see how it would introduce new bugs into the old implementation since >all the relevant code would be #define'd out by the compiler. That is, if >its configured off, the code simply doesnt exist, and you get the old >implementation, pristine. The previous bug I'm referring to didn't occur in kernel code; it was introduced by kernel code changes that resulted in a system header change (and that was the bug). Bugs don't happen where you intend them to. They happen where you weren't paying attention. Stable == Code freeze, period. Monty - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [EMAIL PROTECTED]
- Re: WG: AW: cdrecord problems on recent Linux versions Joerg Schilling
- Re: WG: AW: cdrecord problems on recent Linux versio... Richard Gooch
- Re: WG: AW: cdrecord problems on recent Linux versions Joerg Schilling
- Re: WG: AW: cdrecord problems on recent Linux versio... Richard Gooch
- Re: WG: AW: cdrecord problems on recent Linux ve... Monty
- Re: WG: AW: cdrecord problems on recent Linu... Richard Gooch
- Re: WG: AW: cdrecord problems on recent ... Monty
- Re: WG: AW: cdrecord problems on re... Dan Hollis
- Re: WG: AW: cdrecord problems o... Monty
- Re: WG: AW: cdrecord problems o... Dan Hollis
- Re: WG: AW: cdrecord problems o... Monty
- Re: WG: AW: cdrecord problems o... Dan Hollis
- Re: WG: AW: cdrecord problems o... Richard Gooch
- Re: WG: AW: cdrecord problems o... Theodore Y. Ts'o
- Re: WG: AW: cdrecord problems o... Richard Gooch
- Re: WG: AW: cdrecord problems o... Theodore Y. Ts'o
- Re: WG: AW: cdrecord problems o... Richard Gooch
- Re: WG: AW: cdrecord problems o... Richard Gooch
- Re: WG: AW: cdrecord problems o... Monty
- Re: WG: AW: cdrecord problems o... Richard Gooch
- No Subject owner-linux-scsi
