All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Verych <olecom@flower.upol.cz>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, josh@kernel.org
Subject: Re: [PATCH] CodingStyle: Add information about trailing whitespace.
Date: Thu, 28 Jun 2007 00:14:38 +0200	[thread overview]
Message-ID: <E1I3fmY-0003A8-8D@flower> (raw)
In-Reply-To: <20070627123122.257661e3.akpm@linux-foundation.org>

> Newsgroups: gmane.linux.kernel
> Date: Wed, 27 Jun 2007 12:31:22 -0700

><checks>
>
> akpm:/usr/src/25> grep -l "^+.*[        ]$" patches/git-*.patch
> patches/git-acpi.patch
> patches/git-alsa.patch
> patches/git-battery.patch
> patches/git-cifs.patch
> patches/git-drm.patch
> patches/git-gfs2-nmw.patch
> patches/git-hid.patch
> patches/git-ipwireless_cs.patch
> patches/git-ixgbe.patch
> patches/git-kgdb.patch
> patches/git-leds.patch
> patches/git-libata-all.patch
> patches/git-md-accel.patch
> patches/git-netdev-all.patch
> patches/git-newsetup.patch
> patches/git-nfs.patch
> patches/git-ocfs2.patch
> patches/git-pciseg.patch
> patches/git-qla3xxx.patch
> patches/git-selinux.patch
> patches/git-sym2.patch
> patches/git-unionfs.patch
> patches/git-watchdog.patch
> patches/git-wireless.patch
>
> damn.  Bunch of lamers.

    9. The editor is the primary tool for programmers. People who don't
       choose an appropriate primary tool are worthless as professionals.

among others in <http://quimby.gnus.org/circus/notes/programming.html>

I've shared little sh script too, 4 + 2(optional) sed commands with
comments of what whitespace crap was spotted. Yet nothing happened.
Converse -- questions about why they are useless...

Introduction of editor's labels in C files is the most outrages thing.
Don't editors smart to see filename extensions first? If they don't, fix
editors, not sources!

> But there's less than there used to be.
____

  parent reply	other threads:[~2007-06-27 22:01 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-27 17:59 [PATCH] CodingStyle: Add information about trailing whitespace Josh Triplett
2007-06-27 18:05 ` Chris Shoemaker
2007-06-27 18:17   ` Josh Triplett
2007-06-27 19:32     ` Chris Shoemaker
2007-06-27 22:18   ` Jan Engelhardt
2007-06-28  6:00     ` dave young
2007-06-28  6:08       ` Josh Triplett
2007-06-28  6:29         ` dave young
2007-06-28  6:52           ` Jan Engelhardt
2007-06-28  6:58             ` Josh Triplett
2007-06-28  7:08               ` Li Yang-r58472
2007-06-28  7:10                 ` Dave Young
2007-06-28  7:20                   ` Dave Young
2007-06-29  3:11                     ` [OT] Vim highlighting for trailing spaces Kyle Moffett
2007-06-29  7:39                       ` Jan Engelhardt
2007-06-29  7:53                         ` Josh Triplett
2007-06-29  8:01                           ` Jan Engelhardt
2007-06-29  8:42                             ` Josh Triplett
2007-06-29  9:21                               ` Björn Steinbrink
2007-06-29  9:26                                 ` Dave Young
2007-06-29 12:40                       ` Michael Tokarev
2007-06-29 12:49                         ` Dmitry Torokhov
2007-06-30  0:00                           ` Kyle Moffett
2007-06-29  2:03               ` [PATCH] CodingStyle: Add information about trailing whitespace Andy Isaacson
2007-06-27 19:31 ` Andrew Morton
2007-06-27 22:14   ` Jan Engelhardt
2007-06-27 22:14   ` Oleg Verych [this message]
     [not found]   ` <1183138323.17622.9.camel@shinybook.infradead.org>
     [not found]     ` <20070629175204.GA1341@zarina>
     [not found]       ` <1183142639.1170.371.camel@pmac.infradead.org>
2007-06-29 19:31         ` Anton Vorontsov
2007-06-29 22:52           ` Henrique de Moraes Holschuh

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=E1I3fmY-0003A8-8D@flower \
    --to=olecom@flower.upol.cz \
    --cc=akpm@linux-foundation.org \
    --cc=josh@kernel.org \
    --cc=linux-kernel@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.