All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Knutsson <ricknu-0@student.ltu.se>
To: Oleg Verych <olecom@flower.upol.cz>, Andrew Morton <akpm@osdl.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [SCRIPT] Remove "space damage" from patches
Date: Mon, 29 Jan 2007 02:26:04 +0100	[thread overview]
Message-ID: <45BD4D2C.2010306@student.ltu.se> (raw)
In-Reply-To: <slrnerqgj0.f71.olecom@flower.upol.cz>

Oleg Verych wrote:
> 29-01-2007, Richard Knutsson:
>   
>> Oleg Verych wrote:
>>     
>>> Nack, big and fat. It's userspace problem.
>>>
>>> If our "developers" can't use or update their every-day-tools, it's a
>>> shame. And this is not trolling: i'm using Jed and GNU Emacs, both are
>>> ok with whitespace "production".
>>>       
>> Oh, I hope I didn't give the impression I wanted it in the kernel (that 
>> is why i labeled it as SCRIPT and not PATCH), as you said it is a 
>> userspace problem. I just thought a simple script to remove those 
>> whitespace could help in an imperfect world. I prefer kate since then 
>> you can see where the tabs begins (and other features).
>>     
>
> Just to give you idea, how imperfect it is:
> <http://marc.theaimsgroup.com/?l=linux-mm-commits&m=116198944205036&w=2>
>
> Anyway, i still think programmers *must* take care of it, if they think
> they _are_ Programmers. IMHO LKML already gives obligation to be one
Then I hope you don't mind me asking, why is there (L)indent? Everyone 
can make a mistake and if your editor does not auto-format then there 
may be a whitespace straying.
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. 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 ;) ).

As I said in the posting, it is just if someone is interested in it, 
otherwise you have a Del-button.

Richard Knutsson


  reply	other threads:[~2007-01-29  1:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-28 21:37 [SCRIPT] Remove "space damage" from patches 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 [this message]
2007-01-29  1:43         ` Oleg Verych
2007-01-29  2:00           ` Richard Knutsson
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=45BD4D2C.2010306@student.ltu.se \
    --to=ricknu-0@student.ltu.se \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olecom@flower.upol.cz \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.