Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Phil Muldoon <pmuldoon@redhat.com>
To: gdb@sourceware.org
Subject: Re: Trailing Whitespace
Date: Thu, 09 Jan 2014 14:57:00 -0000	[thread overview]
Message-ID: <20140109145731.GA13720@localhost.localdomain> (raw)
In-Reply-To: <20140109144455.GA2972@blade.nx>

On Thu, 09 Jan 2014, Gary Benson wrote:

> Ben Longbons wrote:
> > Therefore, I suggest that someone create a commit that removes all
> > the trailing whitespace. The pressing need is to apply this to gdb/
> > but there is no reason it couldn't be applied to other parts if need
> > be.
 
> I see nobody replied to this, but it would be pretty nice to have the
> repo cleaned in this way.
> 
> Does anybody have any reason not to do this?

Whitespace cleanups inevitably bit-rot unless the maintainer checks
each and every patch for whitespace.  This is pretty easy to do in
emacs, but I am not so sure about other editors.  It's another weight
on the already burdened shoulders of maintainers.

The simple way to make sure that your patch does not have useless
whitespace included is to run:

git diff --check

That will flag all the whitespace.

Also (and I am not sure if git can get around this somehow) whitespace
cleanups tend to obliterate diffs/patches that were written before the
cleanup took place.  This makes merging a massive pain.

So my 2 pence worth is, no, not a good idea ;)

Cheers,

Phil


  reply	other threads:[~2014-01-09 14:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-19  0:19 Ben Longbons
2014-01-09 14:45 ` Gary Benson
2014-01-09 14:57   ` Phil Muldoon [this message]
2014-01-09 15:01     ` Joel Brobecker
2014-01-09 18:46       ` Dmitry Samersoff
2014-01-10  3:44         ` Samuel Bronson
2014-01-10  4:00           ` Joel Brobecker

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=20140109145731.GA13720@localhost.localdomain \
    --to=pmuldoon@redhat.com \
    --cc=gdb@sourceware.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