Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: [RFA] Remove obsolete info in README (remote-vx)
Date: Mon, 20 Nov 2006 18:07:00 -0000	[thread overview]
Message-ID: <20061120180707.GF3329@adacore.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 503 bytes --]

The files mentioned in that section have been removed in 2004.

The paragraph I propose to delete mentions that this code can be
used as an example for communication via ethernet. Do we have
another such example? Is this still relevant? (could we use ser-tcp
in the remote stub for instance?)

2006-11-20  Joel Brobecker  <brobecker@adacore.com>

        * README: Remove obsolete information.

OK to apply? (will apply to the branch the patch that will actually
be committed to head)

Thanks,
-- 
Joel

[-- Attachment #2: README.diff --]
[-- Type: text/plain, Size: 913 bytes --]

Index: README
===================================================================
RCS file: /cvs/src/src/gdb/README,v
retrieving revision 1.37
diff -u -p -r1.37 README
--- README	8 Aug 2006 20:26:23 -0000	1.37
+++ README	20 Nov 2006 17:59:28 -0000
@@ -1,5 +1,5 @@
 		     README for gdb-6.3 release
-		Updated 8, November, 2004 by Andrew Cagney
+		     Updated 20, November, 2006
 
 This is GDB, the GNU source-level debugger.
 
@@ -462,12 +462,6 @@ monitors and other hardware:
 	remote-sds.c	 PowerPC SDS monitor
 	remote-sim.c	 Generalized simulator protocol
 	remote-st.c	 Tandem ST-2000 monitor
-	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.
 
 
 Reporting Bugs in GDB

             reply	other threads:[~2006-11-20 18:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-20 18:07 Joel Brobecker [this message]
2006-11-20 18:29 ` Daniel Jacobowitz
2006-11-20 20:24 ` Eli Zaretskii
2006-11-21  5:16   ` Joel Brobecker

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=20061120180707.GF3329@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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