Re: Whining about MIME formatted email
Jes Sorensen wrote: > So? I have one of those letters in my name as well, doesn't mean I put > it in the From line or in the code that I write. Or do you want us all > to start using a compiler and editors that will understand full UTF8 > so everybody who use non roman character sets have their names > displayed correctly in the comments of the code? > > The kernel is written in C, C is in ASCII so whats the problem? Look at the kernel. There are already a few comments using 8 bit chars. One presumes iso-latin-1. -- Jamie - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: [OT] Re: Whining about MIME formatted email
> "David" == David Ford <[EMAIL PROTECTED]> writes: David> C program instructions are in ASCII, data certainly isn't David> restricted to that. If you or your M*A can't or won't deal David> with anything but plain text, then filter it. Plain text is David> clearly in the minority of emails throughout the world and the David> people on LKML seem in general not to care about MIME and David> frequently use it. Let's end this offtopic thread please. Says the guy who puts his response in front of the quoted text which violates rfc1855 and adds a vcard you really expect people to take you serious? Jes - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: [OT] Re: Whining about MIME formatted email
On Tue, 12 Sep 2000, David Ford wrote: > C program instructions are in ASCII, data certainly isn't restricted to that. > If you or your M*A can't or won't deal with anything but plain text, then > filter it. Plain text is clearly in the minority of emails throughout the > world and the people on LKML seem in general not to care about MIME and > frequently use it. Let's end this offtopic thread please. Good. Now, could you please get something resembling a MUA or at least RTFM to figure out how to make Mozilla cut this "card for foobar" crap? "X-Terminally-Clueless: yes" in headers would convey precisely the same message and would have a benefit of being shorter. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
[OT] Re: Whining about MIME formatted email
C program instructions are in ASCII, data certainly isn't restricted to that. If you or your M*A can't or won't deal with anything but plain text, then filter it. Plain text is clearly in the minority of emails throughout the world and the people on LKML seem in general not to care about MIME and frequently use it. Let's end this offtopic thread please. -d Jes Sorensen wrote: > The kernel is written in C, C is in ASCII so whats the problem? -- "The difference between 'involvement' and 'commitment' is like an eggs-and-ham breakfast: the chicken was 'involved' - the pig was 'committed'." begin:vcard n:Ford;David x-mozilla-html:TRUE org:http://www.kalifornia.com/images/paradise.jpg"> adr:;; version:2.1 email;internet:[EMAIL PROTECTED] title:Blue Labs Developer x-mozilla-cpt:;-12480 fn:David Ford end:vcard
Re: Whining about MIME formatted email
> "Horst" == Horst von Brand <[EMAIL PROTECTED]> writes: Horst> "Albert D. Cahalan" <[EMAIL PROTECTED]> said: [...] >> That would be the "H=F8jland" in your .sig, right? No problem, '=' >> is a standard character. >> >> My MUA has been RFC-compliant since before this "MIME" thing >> existed, so I can see the full ASCII character set. That includes >> the carat, underscore, back tick, backslash, vertical bar, at >> symbol, octothorpe, and both braces. Horst> That is a really upsetting US/ASCII/English-centric view. How Horst> would you feel if the prevalent, "standard" character set Horst> didn't include 'h' and _your_ name showed up as "Albert Horst> D. Ca=68alan" elsewhere?! So? I have one of those letters in my name as well, doesn't mean I put it in the From line or in the code that I write. Or do you want us all to start using a compiler and editors that will understand full UTF8 so everybody who use non roman character sets have their names displayed correctly in the comments of the code? The kernel is written in C, C is in ASCII so whats the problem? Jes - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Whining about MIME formatted email
> "Kurt" == Kurt Garloff <[EMAIL PROTECTED]> writes: Kurt> On Fri, Sep 08, 2000 at 06:33:34PM +1100, Keith Owens wrote: >> Exmh handles MIME just fine and MIME is useful for some things. >> Other people (including Linus) have made it clear that MIME is not >> welcome on linux-kernel, plain text format is always better when >> you are sending plain text. What next, rich text format and HTML >> with multiple copies of the text, MSWord format? Kurt> Stop making stupid statements like this, please, and comparing Kurt> well-defined RFC standards with proprietary formats. MIME is a Kurt> way for people that happen to use non 7bit characters to be able Kurt> to print their name correctly, even in presence of MTAs Kurt> somewhere in between that don't handle 8bit. Or with PGP, which Kurt> also prefers 7bit ... You'll probably complain about me using a Kurt> GnuPG signature as well. You do not need 8 bit characters in kernel code it's as simple as that. If you really insist, then post the patch in pure 8 bit, quoted-unreadable is brain damage and deserves to die the sooner the better. If there is a broken mail server somewhere in the way (which is really really rare these days) let the people who are behind that server suffer and not everybody else. Besides, quoted-unreadable makes it hard to just do patch < $MAILDIR/linux-kernel/ Jes - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Whining about MIME formatted email
"Horst" == Horst von Brand [EMAIL PROTECTED] writes: Horst "Albert D. Cahalan" [EMAIL PROTECTED] said: [...] That would be the "H=F8jland" in your .sig, right? No problem, '=' is a standard character. My MUA has been RFC-compliant since before this "MIME" thing existed, so I can see the full ASCII character set. That includes the carat, underscore, back tick, backslash, vertical bar, at symbol, octothorpe, and both braces. Horst That is a really upsetting US/ASCII/English-centric view. How Horst would you feel if the prevalent, "standard" character set Horst didn't include 'h' and _your_ name showed up as "Albert Horst D. Ca=68alan" elsewhere?! So? I have one of those letters in my name as well, doesn't mean I put it in the From line or in the code that I write. Or do you want us all to start using a compiler and editors that will understand full UTF8 so everybody who use non roman character sets have their names displayed correctly in the comments of the code? The kernel is written in C, C is in ASCII so whats the problem? Jes - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
[OT] Re: Whining about MIME formatted email
C program instructions are in ASCII, data certainly isn't restricted to that. If you or your M*A can't or won't deal with anything but plain text, then filter it. Plain text is clearly in the minority of emails throughout the world and the people on LKML seem in general not to care about MIME and frequently use it. Let's end this offtopic thread please. -d Jes Sorensen wrote: The kernel is written in C, C is in ASCII so whats the problem? -- "The difference between 'involvement' and 'commitment' is like an eggs-and-ham breakfast: the chicken was 'involved' - the pig was 'committed'." begin:vcard n:Ford;David x-mozilla-html:TRUE org:img src="http://www.kalifornia.com/images/paradise.jpg" adr:;; version:2.1 email;internet:[EMAIL PROTECTED] title:Blue Labs Developer x-mozilla-cpt:;-12480 fn:David Ford end:vcard
Re: [OT] Re: Whining about MIME formatted email
On Tue, 12 Sep 2000, David Ford wrote: C program instructions are in ASCII, data certainly isn't restricted to that. If you or your M*A can't or won't deal with anything but plain text, then filter it. Plain text is clearly in the minority of emails throughout the world and the people on LKML seem in general not to care about MIME and frequently use it. Let's end this offtopic thread please. Good. Now, could you please get something resembling a MUA or at least RTFM to figure out how to make Mozilla cut this "card for foobar" crap? "X-Terminally-Clueless: yes" in headers would convey precisely the same message and would have a benefit of being shorter. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: [OT] Re: Whining about MIME formatted email
"David" == David Ford [EMAIL PROTECTED] writes: David C program instructions are in ASCII, data certainly isn't David restricted to that. If you or your M*A can't or won't deal David with anything but plain text, then filter it. Plain text is David clearly in the minority of emails throughout the world and the David people on LKML seem in general not to care about MIME and David frequently use it. Let's end this offtopic thread please. Says the guy who puts his response in front of the quoted text which violates rfc1855 and adds a vcard you really expect people to take you serious? Jes - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Whining about MIME formatted email
Jes Sorensen wrote: So? I have one of those letters in my name as well, doesn't mean I put it in the From line or in the code that I write. Or do you want us all to start using a compiler and editors that will understand full UTF8 so everybody who use non roman character sets have their names displayed correctly in the comments of the code? The kernel is written in C, C is in ASCII so whats the problem? Look at the kernel. There are already a few comments using 8 bit chars. One presumes iso-latin-1. -- Jamie - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Whining about MIME formatted email
Alexander Viro writes: > MIME may help to work around the b0rken MTAs that are not 8-bit > clean, but that's about it. It is nothing but a glamorized tarball. MIME and glamour are like oil and water. Regards, Richard Permanent: [EMAIL PROTECTED] Current: [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Whining about MIME formatted email
Alexander Viro writes: MIME may help to work around the b0rken MTAs that are not 8-bit clean, but that's about it. It is nothing but a glamorized tarball. MIME and glamour are like oil and water. Regards, Richard Permanent: [EMAIL PROTECTED] Current: [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Whining about MIME formatted email
On Sat, 9 Sep 2000, Horst von Brand wrote: > "Albert D. Cahalan" <[EMAIL PROTECTED]> said: > > [...] > > > That would be the "H=F8jland" in your .sig, right? > > No problem, '=' is a standard character. > > > > My MUA has been RFC-compliant since before this "MIME" thing existed, > > so I can see the full ASCII character set. That includes the carat, > > underscore, back tick, backslash, vertical bar, at symbol, octothorpe, > > and both braces. > > That is a really upsetting US/ASCII/English-centric view. How would you > feel if the prevalent, "standard" character set didn't include 'h' and > _your_ name showed up as "Albert D. Ca=68alan" elsewhere?! Oh, come on. You are lucky enough to have the alphabet derived from Latin. > That your MUA is RFC-compliant is nice, but in this case the RFC was > shortsighted. My MUA and MTA are at least able to handle Latin-1 (and > probably other charsets too, never tried). Yes? How about we all settle down on UTF-8? MIME may be a good thing or not, but it's _not_ a solution for internationalization problems. No more than uuencoded tarball would be. Care to tell me how to put Latin-1 and Cyrillic into the same text? No? Thought so. How about adding Greek into the mix? Separate piece for every place where you change the alphabet? Use of MIME for that is a bad kludge. It happens to work for English+one more language cominations. Try it for French+Russian and you are in for trouble. MIME may help to work around the b0rken MTAs that are not 8-bit clean, but that's about it. It is nothing but a glamorized tarball. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Whining about MIME formatted email
"Albert D. Cahalan" <[EMAIL PROTECTED]> said: [...] > That would be the "H=F8jland" in your .sig, right? > No problem, '=' is a standard character. > > My MUA has been RFC-compliant since before this "MIME" thing existed, > so I can see the full ASCII character set. That includes the carat, > underscore, back tick, backslash, vertical bar, at symbol, octothorpe, > and both braces. That is a really upsetting US/ASCII/English-centric view. How would you feel if the prevalent, "standard" character set didn't include 'h' and _your_ name showed up as "Albert D. Ca=68alan" elsewhere?! That your MUA is RFC-compliant is nice, but in this case the RFC was shortsighted. My MUA and MTA are at least able to handle Latin-1 (and probably other charsets too, never tried). -- Horst von Brand [EMAIL PROTECTED] Casilla 9G, Vin~a del Mar, Chile +56 32 672616 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Whining about MIME formatted email
Albert D. Cahalan wrote: > > You can say it louder but you can't say it clearer. I'd love to know that > > my surname shows up correctly everywhere. BTW, mutt shows MIME > > patches in plain text without any problems > > That would be the "H=F8jland" in your .sig, right? > No problem, '=' is a standard character. Time to upgrade your MUA. Ragnar's name looks fine to me :-) Though somehow I don't think Chinese would come out right on my xterm. > My MUA has been RFC-compliant since before this "MIME" thing existed, > so I can see the full ASCII character set. Yeah, and I bet Linux 0.99's TCP was RFC793 compliant too but that doesn't cut it these days either. -- Jamie - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Whining about MIME formatted email
Albert D. Cahalan wrote: You can say it louder but you can't say it clearer. I'd love to know that my surname shows up correctly everywhere. asbestos BTW, mutt shows MIME patches in plain text without any problems / That would be the "H=F8jland" in your .sig, right? No problem, '=' is a standard character. Time to upgrade your MUA. Ragnar's name looks fine to me :-) Though somehow I don't think Chinese would come out right on my xterm. My MUA has been RFC-compliant since before this "MIME" thing existed, so I can see the full ASCII character set. Yeah, and I bet Linux 0.99's TCP was RFC793 compliant too but that doesn't cut it these days either. -- Jamie - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Whining about MIME formatted email
"Albert D. Cahalan" [EMAIL PROTECTED] said: [...] That would be the "H=F8jland" in your .sig, right? No problem, '=' is a standard character. My MUA has been RFC-compliant since before this "MIME" thing existed, so I can see the full ASCII character set. That includes the carat, underscore, back tick, backslash, vertical bar, at symbol, octothorpe, and both braces. That is a really upsetting US/ASCII/English-centric view. How would you feel if the prevalent, "standard" character set didn't include 'h' and _your_ name showed up as "Albert D. Ca=68alan" elsewhere?! That your MUA is RFC-compliant is nice, but in this case the RFC was shortsighted. My MUA and MTA are at least able to handle Latin-1 (and probably other charsets too, never tried). -- Horst von Brand [EMAIL PROTECTED] Casilla 9G, Vin~a del Mar, Chile +56 32 672616 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Whining about MIME formatted email
On Sat, 9 Sep 2000, Horst von Brand wrote: "Albert D. Cahalan" [EMAIL PROTECTED] said: [...] That would be the "H=F8jland" in your .sig, right? No problem, '=' is a standard character. My MUA has been RFC-compliant since before this "MIME" thing existed, so I can see the full ASCII character set. That includes the carat, underscore, back tick, backslash, vertical bar, at symbol, octothorpe, and both braces. That is a really upsetting US/ASCII/English-centric view. How would you feel if the prevalent, "standard" character set didn't include 'h' and _your_ name showed up as "Albert D. Ca=68alan" elsewhere?! Oh, come on. You are lucky enough to have the alphabet derived from Latin. That your MUA is RFC-compliant is nice, but in this case the RFC was shortsighted. My MUA and MTA are at least able to handle Latin-1 (and probably other charsets too, never tried). Yes? How about we all settle down on UTF-8? MIME may be a good thing or not, but it's _not_ a solution for internationalization problems. No more than uuencoded tarball would be. Care to tell me how to put Latin-1 and Cyrillic into the same text? No? Thought so. How about adding Greek into the mix? Separate piece for every place where you change the alphabet? Use of MIME for that is a bad kludge. It happens to work for English+one more language cominations. Try it for French+Russian and you are in for trouble. MIME may help to work around the b0rken MTAs that are not 8-bit clean, but that's about it. It is nothing but a glamorized tarball. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Whining about MIME formatted email
Ragnar Hojland Esp writes: > On Fri, Sep 08, 2000 at 11:10:13PM +0200, Kurt Garloff wrote: > > Stop making stupid statements like this, please, and comparing well-d= > efined > > RFC standards with proprietary formats.=20 > > MIME is a way for people that happen to use non 7bit characters to be= > able > > to print their name correctly, even in presence of MTAs somewhere in = > between > > You can say it louder but you can't say it clearer. I'd love to know t= > hat > my surname shows up correctly everywhere. BTW, mutt shows M= > IME > patches in plain text without any problems That would be the "H=F8jland" in your .sig, right? No problem, '=' is a standard character. My MUA has been RFC-compliant since before this "MIME" thing existed, so I can see the full ASCII character set. That includes the carat, underscore, back tick, backslash, vertical bar, at symbol, octothorpe, and both braces. > --=20 > /| Ragnar H=F8jland Freedom - Linux - OpenGL Fingerprint = > 94C4B > \ o.O| 2F0D27DE025BE2= > 302C > =3D(_)=3D "Thou shalt not follow the NULL pointer for 104B78C56 = > B72F0822 >U chaos and madness await thee at its end." hkp://keys.pgp= > =2Ecom > > Handle via comment channels only. > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel"= > in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Whining about MIME formatted email
On Fri, Sep 08, 2000 at 11:10:13PM +0200, Kurt Garloff wrote: > Stop making stupid statements like this, please, and comparing well-defined > RFC standards with proprietary formats. > MIME is a way for people that happen to use non 7bit characters to be able > to print their name correctly, even in presence of MTAs somewhere in between You can say it louder but you can't say it clearer. I'd love to know that my surname shows up correctly everywhere. BTW, mutt shows MIME patches in plain text without any problems -- /| Ragnar Højland Freedom - Linux - OpenGL Fingerprint 94C4B \ o.O| 2F0D27DE025BE2302C =(_)= "Thou shalt not follow the NULL pointer for 104B78C56 B72F0822 U chaos and madness await thee at its end." hkp://keys.pgp.com Handle via comment channels only. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Whining about MIME formatted email
On Fri, Sep 08, 2000 at 06:33:34PM +1100, Keith Owens wrote: > Exmh handles MIME just fine and MIME is useful for some things. Other > people (including Linus) have made it clear that MIME is not welcome on > linux-kernel, plain text format is always better when you are sending > plain text. What next, rich text format and HTML with multiple copies > of the text, MSWord format? Stop making stupid statements like this, please, and comparing well-defined RFC standards with proprietary formats. MIME is a way for people that happen to use non 7bit characters to be able to print their name correctly, even in presence of MTAs somewhere in between that don't handle 8bit. Or with PGP, which also prefers 7bit ... You'll probably complain about me using a GnuPG signature as well. Regards, -- Kurt Garloff <[EMAIL PROTECTED]> Eindhoven, NL GPG key: See mail header, key servers Linux kernel development SuSE GmbH, Nuernberg, FRG SCSI, Security PGP signature
Re: Whining about MIME formatted email
On Fri, Sep 08, 2000 at 06:33:34PM +1100, Keith Owens wrote: > plain text. What next, rich text format and HTML with multiple copies > of the text, MSWord format? don't joke. a certain government department here (that shall remain unnamed) has an email system that *automatically* converts everything to rtf. it's, well, yuk? :-( j. -- john slee <[EMAIL PROTECTED]> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Whining about MIME formatted email
On Fri, Sep 08, 2000 at 06:33:34PM +1100, Keith Owens wrote: Exmh handles MIME just fine and MIME is useful for some things. Other people (including Linus) have made it clear that MIME is not welcome on linux-kernel, plain text format is always better when you are sending plain text. What next, rich text format and HTML with multiple copies of the text, MSWord format? Stop making stupid statements like this, please, and comparing well-defined RFC standards with proprietary formats. MIME is a way for people that happen to use non 7bit characters to be able to print their name correctly, even in presence of MTAs somewhere in between that don't handle 8bit. Or with PGP, which also prefers 7bit ... You'll probably complain about me using a GnuPG signature as well. Regards, -- Kurt Garloff [EMAIL PROTECTED] Eindhoven, NL GPG key: See mail header, key servers Linux kernel development SuSE GmbH, Nuernberg, FRG SCSI, Security PGP signature
Re: Whining about MIME formatted email
On Fri, Sep 08, 2000 at 11:10:13PM +0200, Kurt Garloff wrote: Stop making stupid statements like this, please, and comparing well-defined RFC standards with proprietary formats. MIME is a way for people that happen to use non 7bit characters to be able to print their name correctly, even in presence of MTAs somewhere in between You can say it louder but you can't say it clearer. I'd love to know that my surname shows up correctly everywhere. asbestos BTW, mutt shows MIME patches in plain text without any problems / -- /| Ragnar Højland Freedom - Linux - OpenGL Fingerprint 94C4B \ o.O| 2F0D27DE025BE2302C =(_)= "Thou shalt not follow the NULL pointer for 104B78C56 B72F0822 U chaos and madness await thee at its end." hkp://keys.pgp.com Handle via comment channels only. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Whining about MIME formatted email
Ragnar Hojland Esp writes: On Fri, Sep 08, 2000 at 11:10:13PM +0200, Kurt Garloff wrote: Stop making stupid statements like this, please, and comparing well-d= efined RFC standards with proprietary formats.=20 MIME is a way for people that happen to use non 7bit characters to be= able to print their name correctly, even in presence of MTAs somewhere in = between You can say it louder but you can't say it clearer. I'd love to know t= hat my surname shows up correctly everywhere. asbestos BTW, mutt shows M= IME patches in plain text without any problems / That would be the "H=F8jland" in your .sig, right? No problem, '=' is a standard character. My MUA has been RFC-compliant since before this "MIME" thing existed, so I can see the full ASCII character set. That includes the carat, underscore, back tick, backslash, vertical bar, at symbol, octothorpe, and both braces. --=20 /| Ragnar H=F8jland Freedom - Linux - OpenGL Fingerprint = 94C4B \ o.O| 2F0D27DE025BE2= 302C =3D(_)=3D "Thou shalt not follow the NULL pointer for 104B78C56 = B72F0822 U chaos and madness await thee at its end." hkp://keys.pgp= =2Ecom Handle via comment channels only. - To unsubscribe from this list: send the line "unsubscribe linux-kernel"= in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
