All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Cromie <jcromie@divsol.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] RFC - trailing whitespace cleanup script
Date: Mon, 18 Jul 2005 18:10:12 +0000	[thread overview]
Message-ID: <42DBF084.3050106@divsol.com> (raw)
In-Reply-To: <42D9C495.2090405@divsol.com>

Domen Puncer wrote:

>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.
>>
>>    
>>
>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 :-) ).
>  
>
OK, nevermind.

and pls disregard msg I just sent, b4 seeing this one.
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors

  parent reply	other threads:[~2005-07-18 18:10 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
2005-07-18 18:03 ` Jim Cromie
2005-07-18 18:10 ` Jim Cromie [this message]
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=42DBF084.3050106@divsol.com \
    --to=jcromie@divsol.com \
    --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.