Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <vladimir@codesourcery.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [patch] Remove unimplemented MI commands [Re: Learn function name by  	its address]
Date: Sun, 28 Jun 2009 06:45:00 -0000	[thread overview]
Message-ID: <h273ev$glu$2@ger.gmane.org> (raw)
In-Reply-To: <8ac60eac0906271144k61bbb6e3sc092d2780dc4192e@mail.gmail.com>

Paul Pluzhnikov wrote:

> On Fri, Jun 26, 2009 at 3:41 PM, Joel Brobecker<brobecker@adacore.com> wrote:
> 
>>> I tend to think that if nobody has implemented these in $X years, then
>>> nobody ever will.  But then, I'm generally also in the "never comment
>>> out code, just delete it" camp.
>>
>> So am I. The code is still around, just in CVS instead of inside
>> a comment.  Leaving it commented out just creates more clutter that
>> tends to stay rather than being fixed. So I really favor deleting.
> 
> Ok, patch attached.

The code patch is fine. Although at least one of those commands is likely
to be implemented within a year (-break-commands), there's no point to
keep it recognized-but-not-implemented for now.

Thanks,
Volodya



  parent reply	other threads:[~2009-06-28  6:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-27 18:44 Paul Pluzhnikov
2009-06-27 19:03 ` Paul Pluzhnikov
2009-06-27 20:43 ` Eli Zaretskii
2009-06-27 20:50   ` Paul Pluzhnikov
2009-06-28  3:18     ` Eli Zaretskii
2009-06-28  4:13       ` Paul Pluzhnikov
2009-06-28 18:01         ` Eli Zaretskii
2009-06-28 19:32           ` Paul Pluzhnikov
     [not found]     ` <83ocs93v20.fsf__10960.3112018251$1246159141$gmane$org@gnu.org>
2009-06-28  6:42       ` Vladimir Prus
2009-06-28 18:16         ` Eli Zaretskii
2009-06-28  6:45 ` Vladimir Prus [this message]
2009-07-01 19:14   ` Stan Shebs

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='h273ev$glu$2@ger.gmane.org' \
    --to=vladimir@codesourcery.com \
    --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