linux-kernel - Re: [SCRIPT] Remove "space damage" from patches

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]

Date:	Mon, 29 Jan 2007 03:00:35 +0100
From:	Richard Knutsson <ricknu-0@...dent.ltu.se>
To:	Oleg Verych <olecom@...wer.upol.cz>
CC:	Andrew Morton <akpm@...l.org>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [SCRIPT] Remove "space damage" from patches

Oleg Verych wrote:
> On Mon, Jan 29, 2007 at 02:26:04AM +0100, Richard Knutsson wrote:
> []
>   
>> I also guess you saw that the script is _not_ for cleaning up 
>> source-files (can be intrusive and is better to be fixed when fixing 
>> something else), but patches.
>>     
>
> IMHO it's dealing with consequences, not cause, and it's even worse.
>   
How many patches is not to fix bugs, it is worse then some strayed 
whitespace but it is due to reality.
The best is, of course, if neither happened but the next best thing is 
to fix it. And if it can be automated, even better (imho).
>> So if a maintainer does not have anything to easily fix those, they
>> might want a simple script to do the work (otherwise I believe they
>> just deleted my mail ;) ).
>>     
>
> I would like to discuss, would you?
>   
I like to discuss but I am not sure what the result would be. Force 
people to use the editors of our choice?
As long people uses valid e-mail-clients when sending patches (or they 
use the script "sendpatchset"), I'm think we have to be satisfied.
But if you have any ideas, I'm listening.

Richard Knutsson

-
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/