Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: mark.kettenis@xs4all.nl, gdb-patches@sourceware.org
Subject: Re: [commit] Mention VAX floating-point support in NEWS
Date: Wed, 02 Nov 2005 05:55:00 -0000	[thread overview]
Message-ID: <20051102051802.GC974@adacore.com> (raw)
In-Reply-To: <ufyqf8xxz.fsf@gnu.org>

> Anyway, I'm amazed that people are so quick in forgetting the bitter
> lessons we all should have learned from such recent events.

That's not correct. I didn't forget what happened in the past, but I
didn't come to the same conclusion as you did. I don't want to let the
example of one person (AFAIK) affect the productivity of the rest.
So far, I have been truly amazed at the positive attitude of all the
maintainers, and at the collaboration that we have.

My view is: Take a chance with your change. It's very easy to commit
a followup change if the wording needs to be improved or to revert it
if it turns out that it was improper. The thing is that it happens
infrequently, so overall, it's less work, so more time to improve GDB.

Now, that being said, I'm not a global maintainer, so it doesn't affect
me. If you guys prefer to enforce RFAs, I won't in the least bit object.
I was just giving my point of view on the matter.

Just as an aside, we at AdaCore use the review-after-commit approach.
This means that unless we're unsure of a change, we commit the change,
and the other engineers then review that change after. Very often the
change will be fine, but we have had occasions where we either had to
improve the change or even revert it. No hard feelings, no wars, it's
just part of human nature to sometimes fail.

-- 
Joel


  reply	other threads:[~2005-11-02  5:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-01  7:31 Mark Kettenis
2005-11-01 19:54 ` Eli Zaretskii
2005-11-01 20:56   ` Daniel Jacobowitz
2005-11-02  4:32     ` Eli Zaretskii
2005-11-01 21:22   ` Mark Kettenis
2005-11-02  4:40     ` Eli Zaretskii
2005-11-01 23:00   ` Joel Brobecker
2005-11-02  5:18     ` Eli Zaretskii
2005-11-02  5:55       ` Joel Brobecker [this message]
2005-11-02 20:34         ` Eli Zaretskii
2005-11-02 23:00           ` Jim Blandy
2005-11-02 23:04             ` Daniel Jacobowitz
2005-11-03  1:34               ` Jim Blandy
2005-11-03  6:58               ` Eli Zaretskii

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=20051102051802.GC974@adacore.com \
    --to=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    /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