linux-kernel - Re: [PATCH] Use a format string for linux

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LFD.2.00.0902280924150.3111@localhost.localdomain>
Date:	Sat, 28 Feb 2009 09:27:07 -0800 (PST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Alex Riesen <raa.lkml@...il.com>
cc:	trivial@...nel.org, Stefan Richter <stefanr@...6.in-berlin.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Use a format string for linux_banner

On Sat, 28 Feb 2009, Alex Riesen wrote:
> > 
> > Please send patches as inline text or at least as plaintext attachment
> > in ascii encoding.  linux/Documentation/email-clients.txt has help.
> 
> Couldn't. Had to either choose the corporate firewal and gmail, or the
> Exchange-thing. Both will corrupt patches, unless send as attachment.
> Decided not to expose the corporate mail address.

Well, I _can_ tell you that I just ignore patches that I can't see 
directly in my email reader. Others may pick them up, but for me it's an 
issue of "ok, I can't easily even see the patch, and the person didn't 
bother to do it right - it's not worth my time".

What people _can_ do is to send it both as a crazy attachment _and_ as 
plaintext. If they plaintext gets corrupted, the attachment still works, 
and the plaintext is at least somethign I can see and thus in my mail 
reader decide whether it's worth my time to save the attachment and look 
at it outside the mail reader.

		Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/