From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org
Subject: Re: [RFA/libiberty] Fix documentation issues in filename_cmp.c
Date: Wed, 11 Apr 2007 07:27:00 -0000 [thread overview]
Message-ID: <20070411072852.GC3648@adacore.com> (raw)
In-Reply-To: <u3b3d50ul.fsf@gnu.org>
> I've seen quite a few of such situations, actually. And in any case,
> good engineering doesn't need examples to know what's Right ;-)
OK, if you've seen some cases where it would have helped, then fine.
Otherwise, I've personally been bitten a couple of times after having
done a change that was The Right Thing and yet unnecessary for the
program at hand. The change itself should have had no effect, and
yet I introduced new bugs... Since then, I'm more careful of introducing
only changes that I need.
--
Joel
prev parent reply other threads:[~2007-04-11 7:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 17:27 Joel Brobecker
2007-04-05 18:36 ` DJ Delorie
2007-04-06 6:02 ` Joel Brobecker
2007-04-05 18:44 ` Eli Zaretskii
2007-04-06 6:10 ` Joel Brobecker
2007-04-06 9:05 ` Eli Zaretskii
2007-04-06 10:00 ` Dave Korn
2007-04-07 17:35 ` Daniel Jacobowitz
2007-04-07 17:52 ` Eli Zaretskii
2007-04-11 7:24 ` Joel Brobecker
2007-04-11 18:28 ` Eli Zaretskii
2007-04-11 20:33 ` Ian Lance Taylor
2007-05-03 15:36 ` [RFA/libiberty] use TOLOWER instead of tolower " Joel Brobecker
2007-05-03 16:31 ` Ian Lance Taylor
2007-05-03 23:40 ` Joel Brobecker
2007-05-04 7:18 ` Eli Zaretskii
2007-04-11 7:27 ` 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=20070411072852.GC3648@adacore.com \
--to=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@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