From: Chris Shoemaker <c.shoemaker@cox.net>
To: Josh Triplett <josht@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org, josh@kernel.org
Subject: Re: [PATCH] CodingStyle: Add information about trailing whitespace.
Date: Wed, 27 Jun 2007 14:05:52 -0400 [thread overview]
Message-ID: <20070627180552.GA746@pe.Belkin> (raw)
In-Reply-To: <1182967160.8970.108.camel@josh-work.beaverton.ibm.com>
On Wed, Jun 27, 2007 at 10:59:20AM -0700, Josh Triplett wrote:
> +Do not leave trailing whitespace at the ends of lines. Some editors with
> +"smart" indentation will insert whitespace at the beginning of new lines as
> +appropriate, so you can start typing the next line of code right away.
> +However, some such editors do not remove the whitespace if you end up not
> +putting a line of code there, such as if you leave a blank line. As a result,
> +you end up with lines containing trailing whitespace.
> +
> +Git will warn you about patches that introduce trailing whitespace, and can
> +optionally strip the trailing whitespace for you; however, if applying a series
> +of patches, this may make later patches in the series fail by changing their
> +context lines.
What I'd really like to see is, _why_ is trailing whitespace
considered harmful? Something about MUAs not preserving it or
something?
-chris
next prev parent reply other threads:[~2007-06-27 18:22 UTC|newest]
Thread overview: 27+ 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 [this message]
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
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=20070627180552.GA746@pe.Belkin \
--to=c.shoemaker@cox.net \
--cc=akpm@linux-foundation.org \
--cc=josh@kernel.org \
--cc=josht@linux.vnet.ibm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox