Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: gdb-patches@sources.redhat.com
Subject: [patch] README: remove references to deleted remote-*.c
Date: Sun, 05 Jan 2003 17:07:00 -0000	[thread overview]
Message-ID: <200301051707.h05H7ko19299@duracef.shout.net> (raw)

This patch removes gdb/README references to deleted remote-*.c files.
All these files are deleted, not just obsolete.

I noticed this while I was writing new text for the next section down,
"Reporting Bugs in GDB".

Testing: I checked for ChangeLog entries about these file deletions.
I'm not failing to see them due to a CVS glitch or something.

I am committing this under the obvious fix rule.

Michael C

===

2003-01-05  Michael Chastain  <mec@shout.net>

	* README: Remove references to deleted remote-*.c files:
	remote-adapt.c, remote-eb.c, remote-mm.c, remote-nindy.c,
	remote-nrom.c, remote-os9k.c, remote-udi.c.

===

Index: README
===================================================================
RCS file: /cvs/src/src/gdb/README,v
retrieving revision 1.22
diff -u -r1.22 README
--- README	5 Sep 2002 12:13:08 -0000	1.22
+++ README	5 Jan 2003 16:47:49 -0000
@@ -449,38 +449,23 @@
    There are a number of remote interfaces for talking to existing ROM
 monitors and other hardware:
 
-	remote-adapt.c	 AMD 29000 "Adapt"
 	remote-array.c   Array Tech RAID controller
 	remote-e7000.c	 Hitachi E7000 ICE
-	remote-eb.c	 AMD 29000 "EBMON"
 	remote-es.c	 Ericsson 1800 monitor
 	remote-est.c	 EST emulator
 	remote-hms.c	 Hitachi Micro Systems H8/300 monitor
 	remote-mips.c	 MIPS remote debugging protocol
-	remote-mm.c	 AMD 29000 "minimon"
-	remote-nindy.c   Intel 960 "Nindy"
-	remote-nrom.c	 NetROM ROM emulator
-	remote-os9k.c	 PC running OS/9000
 	remote-rdi.c	 ARM with Angel monitor
 	remote-rdp.c	 ARM with Demon monitor
 	remote-sds.c	 PowerPC SDS monitor
 	remote-sim.c	 Generalized simulator protocol
 	remote-st.c	 Tandem ST-2000 monitor
-	remote-udi.c	 AMD 29000 using the AMD "Universal Debug Interface"
 	remote-vx.c	 VxWorks realtime kernel
 
    Remote-vx.c and the vx-share subdirectory contain a remote
 interface for the VxWorks realtime kernel, which communicates over TCP
 using the Sun RPC library.  This would be a useful starting point for
 other remote- via-ethernet back ends.
-
-   Remote-udi.c and the 29k-share subdirectory contain a remote
-interface for AMD 29000 programs, which uses the AMD "Universal Debug
-Interface".  This allows GDB to talk to software simulators,
-emulators, and/or bare hardware boards, via network or serial
-interfaces.  Note that GDB only provides an interface that speaks UDI,
-not a complete solution.  You will need something on the other end
-that also speaks UDI.
 
 
 Reporting Bugs in GDB


             reply	other threads:[~2003-01-05 17:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-05 17:07 Michael Elizabeth Chastain [this message]
2003-01-06 17:13 ` Andrew Cagney
2003-01-07  3:19 Michael Elizabeth Chastain
2003-01-08  0:23 ` Andrew Cagney
2003-01-08  0:44 Michael Elizabeth Chastain
2003-01-08  0:57 ` Andrew Cagney
2003-01-08 18:51 Michael Elizabeth Chastain
2003-01-08 19:09 ` Andrew Cagney
2003-01-08 19:14 ` Elena Zannoni
2003-01-08 19:39 Michael Elizabeth Chastain
2003-01-08 19:53 Michael Elizabeth Chastain
2003-01-08 20:43 Michael Elizabeth Chastain

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=200301051707.h05H7ko19299@duracef.shout.net \
    --to=mec@shout.net \
    --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