mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Frans Pop <elendil@planet.nl>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	per.liden@ericsson.com, jon.maloy@ericsson.com,
	allan.stephens@windriver.com, samuel@sortiz.org,
	benh@kernel.crashing.org, linuxppc-dev@ozlabs.org,
	e1000-devel@lists.sourceforge.net
Subject: Re: [PATCH 00/09] net: remove trailing spaces in messages
Date: Wed, 24 Mar 2010 22:30:31 +0100	[thread overview]
Message-ID: <201003242230.34217.elendil@planet.nl> (raw)
In-Reply-To: <20100324.141158.43422101.davem@davemloft.net>

On Wednesday 24 March 2010, David Miller wrote:
> All applied, but I have to make some fixups.
>
> For example, GIT warns about trailing whitespace on any lines that you
> touched so I had to fix those up before putting them into the tree.

I did wonder about fixing that or not. But as the surrounding code also has 
tons of trailing whitespace, I chose to leave things consistently messy.

I'll remove at least trailing whitespace next time.

Thanks David.

      reply	other threads:[~2010-03-24 21:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-24 17:40 Frans Pop
2010-03-24 17:57 ` [PATCH 1/9] net: remove trailing space " Frans Pop
2010-03-24 17:57 ` [PATCH 2/9] tipc: " Frans Pop
2010-03-24 17:57 ` [PATCH 3/9] net/irda: " Frans Pop
2010-03-24 17:57 ` [PATCH 4/9] net/ps3_gelic: " Frans Pop
2010-03-24 17:57 ` [PATCH 5/9] net/smc91xx: " Frans Pop
2010-03-24 17:57 ` [PATCH 6/9] net/tokenring: " Frans Pop
2010-03-24 17:57 ` [PATCH 7/9] net/tulip: " Frans Pop
2010-03-24 17:57 ` [PATCH 8/9] net/intel: " Frans Pop
2010-03-24 17:57 ` [PATCH 9/9] net/various: " Frans Pop
2010-03-24 21:11 ` [PATCH 00/09] net: remove trailing spaces " David Miller
2010-03-24 21:30   ` Frans Pop [this message]

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=201003242230.34217.elendil@planet.nl \
    --to=elendil@planet.nl \
    --cc=allan.stephens@windriver.com \
    --cc=benh@kernel.crashing.org \
    --cc=davem@davemloft.net \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=jon.maloy@ericsson.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=netdev@vger.kernel.org \
    --cc=per.liden@ericsson.com \
    --cc=samuel@sortiz.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
Powered by JetHome