From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Pedro Alves <pedro@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: RFA: change K&R to ISO
Date: Sun, 28 Sep 2008 16:58:00 -0000 [thread overview]
Message-ID: <20080928165731.GG3814@adacore.com> (raw)
In-Reply-To: <m3tzc1s5oj.fsf@fleche.redhat.com>
> Pedro> OK. Obvious even nowadays?
>
> I considered that, but I tend to be conservative when applying the
> obvious rule. Usually I think I only use it for clearly incorrect
> comments, typos, and build breakages. That said, I'm happy to follow
> whatever the gdb guidelines actually are.
I think it's always better to be more conservative than the opposite,
particularly when the change contains a lot of hunks. But on the other
hand, my approach (and this is my opinion, not necessarily the opinion
of the GDB maintainers) has always been that it's not the end of the world
if one small change that was considered obvious by a contributor wasn't
so obvious to someone else. It's pretty easy to back out a change after
the fact.
Back the specific issue of converting from K&R to ISO: The change is
fairly mechanical, so the chances of making a mistake are really small.
Also, adding a review-before-commit step adds to the "cost" of making
the change. Allowing contributors to commit these changes using the
obvious rule can only encourage more of these changes.
--
Joel
prev parent reply other threads:[~2008-09-28 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-26 23:32 Tom Tromey
2008-09-26 23:49 ` Pedro Alves
2008-09-27 4:14 ` Joel Brobecker
2008-09-27 20:24 ` Tom Tromey
2008-09-28 16:58 ` Joel Brobecker [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=20080928165731.GG3814@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=tromey@redhat.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