Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
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:18:00 -0000	[thread overview]
Message-ID: <ufyqf8xxz.fsf@gnu.org> (raw)
In-Reply-To: <20051101225954.GB1107@adacore.com> (message from Joel Brobecker on Tue, 1 Nov 2005 14:59:55 -0800)

> Date: Tue, 1 Nov 2005 14:59:55 -0800
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: Mark Kettenis <mark.kettenis@xs4all.nl>,
> 	gdb-patches@sourceware.org
> 
> In my very humble opinion, I think it will overall cost less energy
> if we let changes like this go in, and deal with the odd case where
> the change is not obvious after all. My reasoning is that these cases
> happen very seldomly as the global maintainers have demonstrated a good
> sense of judgement, and it's always easy to revert if we need to discuss
> this.

I'm sorry to say, but your reasoning flies in the face of our recent
experience.  People (who will remain unnamed) were making
controversial changes to the repository, sometimes even over protests
of fellow maintainers.  As experience would have it, reverting is an
option that is seldom if ever taken; perhaps the reason is that
unilateral reverts will just start a revert war, because the person
whose patches are reverted has write access and can re-commit the
reverted patches.

Even if things don't go this far, reverting a change is something
deemed too radical and harsh (and justly so, IMHO), so I don't think
we should rely on it as part of our procedures.

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


  reply	other threads:[~2005-11-02  4:40 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 [this message]
2005-11-02  5:55       ` Joel Brobecker
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=ufyqf8xxz.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --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