From: A Large Angry SCM <gitzilla@gmail.com>
To: jidanni@jidanni.org
Cc: torvalds@linux-foundation.org, git@vger.kernel.org
Subject: Re: Linus and whitespace
Date: Sun, 01 Feb 2009 17:48:51 -0500 [thread overview]
Message-ID: <498626D3.1020202@gmail.com> (raw)
In-Reply-To: <87fxix3hub.fsf@jidanni.org>
jidanni@jidanni.org wrote:
> Gentlemen, I couldn't help but notice a certain Linus B. Torvalds is
> producing mail with trailing whitespace.
>
> I recall one should (linux-doc-*/Documentation/CodingStyle*:)
> "Get a decent editor and don't leave whitespace at the end of lines."
>
> Indeed, with my GNU Emacs show-trailing-whitespace X-ray
> eyespecs on all day, whitespace becomes screaming purple space, so you
> can't blame me for noticing.
>
> Anyway, I have analyzed his messages,
> (User-Agent: Alpine 2.00 (LFD 1167 2008-08-23))
> and discovered that the whitespace phenomenon almost always occurs if
> the lines are more than 60 characters long, the "danger zone", we might say.
>
> $ perl -nwle 'print length if / $/' recent_linus_postings|
> sort|uniq -c|sort -k 2nr
> 1 77
> 1 76
> 17 75
> 17 74
> 11 73
> 18 72
> 12 71
> 6 70
> 8 69
> 6 68
> 2 67
> 1 66
> 2 64
> 1 63
> 1 40
> 9 2
CodingStyle applies to *patches* not to discussion. In how many of those
emails you analyzed were there any trailing whitespace in a patch?
next prev parent reply other threads:[~2009-02-01 22:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-01 22:36 Linus and whitespace jidanni
2009-02-01 22:48 ` A Large Angry SCM [this message]
2009-02-01 22:56 ` Linus Torvalds
2009-02-02 7:22 ` Johannes Gilger
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=498626D3.1020202@gmail.com \
--to=gitzilla@gmail.com \
--cc=git@vger.kernel.org \
--cc=jidanni@jidanni.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).