On Fri, 21 May 2010 16:48:38 -0400 (EDT), Jonathan Nieder wrote:
I am not the kernel team, but for issues in upstream code, it is
_always_ a good idea to go to upstream directly[1].
To the Debian Kernel Team:
Upon the advice of Jonathan Nieder, I will pursue this directly with
upstream, but
Stephen Powell wrote:
So I'm going to send an e-mail to
linux...@de.ibm.com to report the bug and see what happens.
Oh! I should have read the file header:
* Bugreports.to..: linux...@de.ibm.com
Yes, you have the right address. It seems that get_maintainer.pl
expects files to change
As promised in my original post, I have written a little
utility program to zap the disk labels of minidisks corrupted
by this bug. Running it against all affected disks will allow
existing data to be accessed safely by both types of Linux kernels:
those that have the bug and those that have the
reassign 582281 linux-2.6
tags 582281 + upstream
quit
Stephen Powell wrote:
Now, how do you want to work this? Do you (the Debian Kernel Team)
want to function as an intermediary between me and upstream?
Or would you prefer that I report the problem to upstream myself?
I am not the kernel
4 matches
Mail list logo
