Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: gdb-patches@sources.redhat.com
Cc: "J.T. Conklin" <jtc@acorntoolworks.com>
Subject: Re: [patch] Delete "remote cisco" (aka the "mutant remote protocol")
Date: Mon, 26 Jan 2004 23:13:00 -0000	[thread overview]
Message-ID: <40159F02.2030809@gnu.org> (raw)
In-Reply-To: <3FF9D6B1.7020702@gnu.org>

> Hello,
> 
> This deletes the cisco specific code in "remote.c".  Several comments here:
> 
> - at the time of the original commit (GDB's repository was still Cygnus internal) it received the title "mutant remote protocol" since it was giving off an odor that's now commonly refered to as "eau de HP Merge".
> http://sources.redhat.com/ml/gdb/1999-q3/msg00147.html
> 
> - even CISCO think the code should be deleted
> I'm reliably informed (abet more than a year ago) that even CISCO would prefer to see this code removed.
> 
> - I've been warning people of this for >1 year
> http://sources.redhat.com/ml/gdb/2002-08/msg00071.html
> http://sources.redhat.com/ml/gdb/2002-08/msg00170.html
> 
> I'm going to commit this in a few days once I've re-checked GDB with a non-mutant remote target.
> 
> Only question, are there any bits that deserve to be retained?

I've checked this in.

Andrew

> Index: doc/ChangeLog
> 2004-01-05  Andrew Cagney  <cagney@redhat.com>
> 
> 	* gdb.texinfo (Overview): Delete references to the cisco protocol
> 	including the "N" response.
> 
> 2004-01-05  Andrew Cagney  <cagney@redhat.com>
> 
> 	* remote.c: Update copyright.
> 	(echo_check, quit_flag, cisco_kernel_mode): Delete variables.
> 	(minitelnet_return, tty_input, escape_count): Delete variables.
> 	(remote_cisco_mode): Delete variable.
> 	(remote_cisco_open, remote_cisco_close): Delete function.
> 	(remote_cisco_mourn, remote_cisco_wait): Delete function.
> 	(init_remote_cisco_ops): Delete function.
> 	(_initialize_remote): Do not install "remote cisco" code.
> 	(read_frame): Delete cisco specific code.
> 	(remote_info_process): Delete function.
> 	(remote_wait): Delete cisco specific code.
> 	(remote_cisco_section_offsets): Delete function.
> 	(remote_cisco_objfile_relocate): Delete function.
> 	(remote_async_wait): Delete cisco specific code.
> 	(minitelnet, readtty, readsocket): Delete function.
> 



  parent reply	other threads:[~2004-01-26 23:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-05 21:27 Andrew Cagney
2004-01-06  6:18 ` Eli Zaretskii
2004-01-26 23:13 ` Andrew Cagney [this message]
2004-01-27  8:25   ` Eli Zaretskii
2004-01-27 14:05     ` 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=40159F02.2030809@gnu.org \
    --to=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jtc@acorntoolworks.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