From: Richard Knutsson <ricknu-0@student.ltu.se>
To: LKML <linux-kernel@vger.kernel.org>,
Oleg Verych <olecom@flower.upol.cz>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [SCRIPT] Remove "space damage" from patches
Date: Mon, 29 Jan 2007 01:08:23 +0100 [thread overview]
Message-ID: <45BD3AF7.4070902@student.ltu.se> (raw)
In-Reply-To: <slrnerqapg.f71.olecom@flower.upol.cz>
Oleg Verych wrote:
>> From: Richard Knutsson
>> Newsgroups: gmane.linux.kernel
>> Subject: [SCRIPT] Remove "space damage" from patches
>> Date: Sun, 28 Jan 2007 22:37:01 +0100
>>
>
>
>> Hello Andrew and all
>>
>
> Hallo.
>
>
>> I recently tried "git-apply" on the 2.6.20-rc6-mm1 patch and found it to complain about white-spaces.
>> So as a mean to (hopefully) cut down on these nasty white-spaces (and sometimes tabs) I wrote this
>> little script. All it does is checking (lines that are going to be added) for spaces before tabs
>> and trailing spaces/tabs. I tried it on 2.6.20-rc6-mm1 and it seem to work well
>>
>> If there is someone interested, _please_ take it. Any suggestion are welcomed :)
>>
>> Richard Knutsson
>>
>
> 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).
Richard Knutsson
next prev parent reply other threads:[~2007-01-29 0:08 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 [this message]
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
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=45BD3AF7.4070902@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox