LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Richard Knutsson <ricknu-0@student.ltu.se>
To: Oleg Verych <olecom@flower.upol.cz>
Cc: Andrew Morton <akpm@osdl.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [SCRIPT] Remove "space damage" from patches
Date: Mon, 29 Jan 2007 03:00:35 +0100	[thread overview]
Message-ID: <45BD5543.5020704@student.ltu.se> (raw)
In-Reply-To: <20070129014327.GA25271@flower.upol.cz>

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


  reply	other threads:[~2007-01-29  2:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-28 21:37 Richard Knutsson
2007-01-28 22:52 ` Oleg Verych
2007-01-29  0:08   ` Richard Knutsson
2007-01-29  0:31     ` Oleg Verych
2007-01-29  1:26       ` Richard Knutsson
2007-01-29  1:43         ` Oleg Verych
2007-01-29  2:00           ` Richard Knutsson [this message]
2007-01-29  2:27             ` Oleg Verych

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45BD5543.5020704@student.ltu.se \
    --to=ricknu-0@student.ltu.se \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olecom@flower.upol.cz \
    --subject='Re: [SCRIPT] Remove "space damage" from patches' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).