Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-3 Followup-For: Bug #493479
Well, I've been providing information and making myself and my hardware available to the Linux kernel team for nearly 3 weeks, and today I was provided with a patch that allows development kernels (2.6.27*) to boot without workarounds. The process is nearing completion, so I wanted to come back to Debian and ask a few questions: - Will Lenny use 2.6.26? (If not, the following questions are moot.) - If the Linux kernel team does not push the fix into their stable 2.6.26.X line, is the Debian kernel team interested in such a patch? (It is a bit too soon to know whether the Linux kernel folks will want this for the 2.6.26.X line... the issue has not even been raised yet. I will be raising it soon, but in the meantime I wanted to begin finding out what the Debian policies are... just in case.) - If upstream does not push the fix into stable 2.6.26.X, but Debian is interested in a patch, would you folks be more interested in a patch that reverts back to 2.6.25 behavior (safer?) or a patch which applies the new fix which uses a (possibly riskier?) quirk-based approach? Dave W. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
