From: Paul Mundt <lethal@linux-sh.org>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Simon Horman <horms@verge.net.au>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
spi-devel-general@lists.sourceforge.net,
linux-sh@vger.kernel.org
Subject: Re: [PATCH 1/3] SPI: spi_sh_msiof: cosmetic clean-up
Date: Tue, 25 Jan 2011 14:47:54 +0900 [thread overview]
Message-ID: <20110125054754.GB11673@linux-sh.org> (raw)
In-Reply-To: <AANLkTikJm9TEtzFRxYYVXAHgWV68JPamkg5ip6nk1C9h@mail.gmail.com>
On Mon, Jan 24, 2011 at 10:26:55PM -0700, Grant Likely wrote:
> On Mon, Jan 24, 2011 at 10:02 PM, Simon Horman <horms@verge.net.au> wrote:
> > Surely this is a bug in diff. Or perhaps put more politely,
> > diff isn't smart enough to realise a) this is C and b) xxx: isn't
> > a valid function name in C.
>
> Oh, perhaps. But regardless, it is long-standing behaviour and the
> single space convention is widely used. Nobody seems offended enough
> by it to go and change diff. To see, just do:
>
> git grep '^ [a-zA-Z0-9_]*:'
>
> If it were particularly ugly, or actively dangerous, then I'd be
> against this pattern, but it is neither and it noticeably improves
> diff readability.
>
It's largely a personal preference thing. I personally don't care for the
leading spaces, and remove them whenever I encounter them. I know that
Magnus and some others like to use them however, so generally don't care
one way or the other. I assume general apathy has a lot to do with diff
not being fixed (note that this topic does come up from time to time,
where the general conclusion is that someone should probably do something
about it, at some point in time).
prev parent reply other threads:[~2011-01-25 5:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 15:56 [PATCH 1/3] SPI: spi_sh_msiof: cosmetic clean-up Guennadi Liakhovetski
2011-01-21 17:02 ` Grant Likely
2011-01-21 17:10 ` Guennadi Liakhovetski
2011-01-21 19:12 ` Grant Likely
2011-01-25 5:02 ` Simon Horman
2011-01-25 5:26 ` Grant Likely
2011-01-25 5:47 ` Paul Mundt [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=20110125054754.GB11673@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=g.liakhovetski@gmx.de \
--cc=grant.likely@secretlab.ca \
--cc=horms@verge.net.au \
--cc=linux-sh@vger.kernel.org \
--cc=spi-devel-general@lists.sourceforge.net \
/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).