Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Pedro Alves <pedro@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [gdbserver/commit] fix whitespace.
Date: Mon, 23 Mar 2009 03:54:00 -0000	[thread overview]
Message-ID: <1237774353.25721.27.camel@localhost.localdomain> (raw)
In-Reply-To: <20090323011202.GA9472@adacore.com>

El dom, 22-03-2009 a las 18:12 -0700, Joel Brobecker escribió:
> > I'm also applying these further fixes.
> 
> (I can't help myself, sorry)
> 
> You know, the current whitespace rule has been really bugging me
> since day one. I would be a very very happy camper if we got rid
> of tabs and just used spaces. Tabs make it hard for everything:
> hard to edit/navigate in your editor (unless you have a mode that
> makes it transparent for you?), and harder to read patches
> (space display can get off because of the extra character that is
> being put on the first column of each line of the diff).

FWIW, I agree that using just spaces is saner. But it doesn't bother me
as much.

> Iiiiiiihhh!
> 
> (nervous breakdown)

Since we're in group therapy mode:

What bothers me the most is the insistence on old-fashioned English
"rules" which apparently were taught in schools back then, like the
silly "two spaces after period" mantra, and "the passive voice shall
NEVER be used!!!11!".

The latter may perhaps still apply to current English (I'm not sure),
but it certainly isn't so clear-cut in other languages. In Portuguese, I
believe it's still bad if you heavily use passive voice in a text, but
using it every now and then it's certainly not a problem. It may even be
more appropriate to what you're trying to convey (which is why I use it
occasionally).

There, I said it. I feel better now. :-)
-- 
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center


  parent reply	other threads:[~2009-03-23  2:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-23  0:22 Pedro Alves
2009-03-23  1:12 ` Pedro Alves
2009-03-23  1:26   ` Joel Brobecker
2009-03-23  1:31     ` Pedro Alves
2009-03-23  3:54     ` Thiago Jung Bauermann [this message]
2009-03-23  6:28       ` Eli Zaretskii
2009-03-23  4:24     ` Eli Zaretskii
2009-03-23 12:49     ` Mark Kettenis
2009-03-23 14:30       ` 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=1237774353.25721.27.camel@localhost.localdomain \
    --to=bauerman@br.ibm.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.com \
    /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