start tracking user visible changes

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index a28655cb3fde87264221db12a184e5709e143f31..829fc3aa74abf44ebf83a38420213daf654a7e8d 100644 (file)
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,5 +1,8 @@
 Wed Jun 16 16:08:18 1993  K. Richard Pixley  (rich@sendai.cygnus.com)
 
+       * NEWS: tracking user visible changes starting with
+       vxworks-timeout.
+
        * remote-vx.c (_initialize_vx): rename user settable option from
        rpcTimeout to vxworks-timeout.
 

diff --git a/gdb/NEWS b/gdb/NEWS
index b77a1ea3e22e18b07ad476a7fee52eba4bb51c4f..7c285325410326dafbabd1ebe3ed63201064327f 100644 (file)
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -1,6 +1,16 @@
                What has changed since GDB-3.5?
                (Organized release by release)
 
+*** Changes in GDB-???:
+
+ * User visible changes:
+
+All vxworks based targets now support a user settable option, called
+vxworks-timeout.  This option represents the number of seconds gdb
+should wait for responses to rpc's.  You might want to use this if
+your vxworks target is, perhaps, a slow software simulator or happens
+to be on the far side of a thin network line.
+
 *** Changes in GDB-4.9:
 
  * Testsuite