Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch] Deprecate XM_FILE and TM_FILE
Date: Sat, 04 Sep 2004 12:00:00 -0000	[thread overview]
Message-ID: <01c49276$Blat.v2.2.2$c81daa00@zahav.net.il> (raw)
In-Reply-To: <413898FB.7080502@gnu.org> (message from Andrew Cagney on Fri, 03 Sep 2004 12:16:59 -0400)

> Date: Fri, 03 Sep 2004 12:16:59 -0400
> From: Andrew Cagney <cagney@gnu.org>
> Cc: gdb-patches@sources.redhat.com
> 
> I thought we discussed this with the attached.

Did I miss a point where that discussion concluded that it was okay to
deprecate xm-go32.h right away?

For all I know, that discussion was about the idea in principle, and I
somehow thought that you were offering to write the necessary
configury stuff yourself.  No one ever said to me that the next thing
I'll see is the DJGPP port being deprecated.  That is something I'd
expect to be said explicitly, rather than in a committed patch that
pretends to be ``obvious''.

How in the world can you deprecate a port without first asking its
designated maintainer, and without waiting for his/her explicit
approval??

On a more general note, too many commits lately are too trigger-happy
to my taste.  There are fewer and fewer patches that are thoroughly
discussed and where dissenting views are honored rather than ignored.
For me, that makes the GDB development a much less enjoyable
environment than it was for quite a few years before.


  reply	other threads:[~2004-09-04 12:00 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-02 18:30 Andrew Cagney
2004-09-02 20:26 ` Eli Zaretskii
2004-09-03 16:18   ` Andrew Cagney
2004-09-04 12:00     ` Eli Zaretskii [this message]
2004-09-04 14:27       ` Andrew Cagney
2004-09-04 16:28         ` Eli Zaretskii
2004-09-04 23:20           ` Andrew Cagney
2004-09-05  4:17             ` Eli Zaretskii
2004-09-09 16:05               ` Andrew Cagney
2004-09-09 19:31                 ` Eli Zaretskii
2004-09-09 20:26                   ` Andrew Cagney
2004-09-09 21:15                     ` Eli Zaretskii
2004-09-09 21:26                       ` Joel Brobecker
2004-09-10  9:35                         ` Eli Zaretskii
2004-09-10 12:41                           ` Mark Kettenis
2004-09-10 16:32                             ` Eli Zaretskii
2004-09-12 18:07                               ` Andrew Cagney
2004-09-12 18:36                                 ` Eli Zaretskii
2004-09-13 15:35                                   ` Andrew Cagney
2004-09-13 19:48                                     ` Eli Zaretskii
2004-09-13 21:07                                       ` Andrew Cagney
2004-09-13 21:30                                         ` Joel Brobecker
2004-09-24 22:06                                           ` Andrew Cagney
2004-09-15 12:15                                         ` Eli Zaretskii
2004-09-15 15:54                                           ` Andrew Cagney

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='01c49276$Blat.v2.2.2$c81daa00@zahav.net.il' \
    --to=eliz@gnu.org \
    --cc=cagney@gnu.org \
    --cc=gdb-patches@sources.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