This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [commit] Mention VAX floating-point support in NEWS


> 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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]