From: Domen Puncer <domen@coderock.org>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] RFC - trailing whitespace cleanup script
Date: Mon, 18 Jul 2005 17:06:41 +0000 [thread overview]
Message-ID: <20050718170641.GG2457@homer.coderock.org> (raw)
In-Reply-To: <42D9C495.2090405@divsol.com>
[-- Attachment #1: Type: text/plain, Size: 1807 bytes --]
On 16/07/05 20:38 -0600, Jim Cromie wrote:
> Domen, all,
Hi.
>
> Ive considered running following 1-lineer and submitting per-subsystem
> cleanup patches.
>
> cp -al $tree $tree-clean; perl -pi.bak -e 's/\s+\n//' `find $tree-clean
> -print` > mega-patch
>
>
> the problem with doing so is that lots of whitespace has already been
> cleaned,
> and rc3-kj has presumably been superseded by more whitespace fixes,
> which would result in needless rejects.
>
> So, what Id propose is:
>
> a. just prior to releasing rc4-kj, do an rc4-kj-pre
> b. run script against pre tree.
> c. diff -rup pre pre-clean > mega-patch
> d. manually edit/chop up mega-patch on subsystem boundaries
> e. apply each to pre, release rc4-kj
>
> f. repeat periodically
> g. get janitors to recognize that they should do harder fixes, and leave
> whitespace
> for the robo-janitor / whitespace-roomba
No, no, no, and again no. And I do hate trailing whitespace, I have
it coloured red in vim, so there's really no other way than hating.
So... why not?
- Maintainers will want to kill us, because no patch will apply
anymore.
- It would generate _lots_ of traffic.
- It would make it harder to trace bugs ("try to unapply that patch")
- I could probably think of some more, but first one makes it
obsolete anyways. ;-)
When could whitespace fixes be good?
Maybe on a driver that is in bug-fix-only state and is expected to
stay in kernel for a while (IOW, is not broken :-) ).
>
> BTW
>
> when were kj patches last merged into mainline ?
They don't get merged as a whole, just parts, through appropriate
maintainers.
I will need to send some very old ones to akpm, because it looks
like they won't get merged any other way.
> how often (on average) does this happen ?
Hmm... patch per day? It really depends.
[-- Attachment #2: Type: text/plain, Size: 168 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2005-07-18 17:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-17 2:38 [KJ] RFC - trailing whitespace cleanup script Jim Cromie
2005-07-18 12:00 ` Ricardo Nabinger Sanchez
2005-07-18 13:09 ` walter harms
2005-07-18 14:44 ` Alexey Dobriyan
2005-07-18 16:11 ` Jim Cromie
2005-07-18 17:06 ` Domen Puncer [this message]
2005-07-18 18:03 ` Jim Cromie
2005-07-18 18:10 ` Jim Cromie
2005-07-18 22:58 ` Alexey Dobriyan
2005-07-22 18:14 ` maximilian attems
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=20050718170641.GG2457@homer.coderock.org \
--to=domen@coderock.org \
--cc=kernel-janitors@vger.kernel.org \
/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.