[binutils-gdb] gdb/doc: Remove mention of vCont's default actions

[Pedro Alves <palves at sourceware dot org>]

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=39402e6c64121bdae146e82f6c48f0c0e0d9d26b

commit 39402e6c64121bdae146e82f6c48f0c0e0d9d26b
Author: Pedro Alves <palves@redhat.com>
Date:   Sat Oct 29 16:07:31 2016 +0100

    gdb/doc: Remove mention of vCont's default actions
    
    Discussion with qemu folks suggests that the vCont description could
    be even simpler and clearer.  Given we now say:
    
     For each inferior thread, the leftmost action with a matching
     thread-id is applied.
    
    There's really no need to even talk about "default" actions, which
    raises doubts about whether "default" is special in some way (it's
    not).
    
    See <https://lists.gnu.org/archive/html/qemu-devel/2016-10/msg06944.html>.
    
    gdb/doc/ChangeLog:
    2016-10-29  Pedro Alves  <palves@redhat.com>
    
    	* gdb.texinfo (Packets) <vCont>: Remove mention of default
    	actions.

Diff:
---
 gdb/doc/ChangeLog   | 5 +++++
 gdb/doc/gdb.texinfo | 5 ++---
 2 files changed, 7 insertions(+), 3 deletions(-)

diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index 5e87ac4..3b02742 100644
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,8 @@
+2016-10-29  Pedro Alves  <palves@redhat.com>
+
+	* gdb.texinfo (Packets) <vCont>: Remove mention of default
+	actions.
+
 2016-10-26  Pedro Alves  <palves@redhat.com>
 
 	* gdb.texinfo (Packets): Clarify vCont packets with multiple
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index d636a16..df548dc 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -35538,9 +35538,8 @@ syntax described in @ref{thread-id syntax}.  If multiprocess
 extensions (@pxref{multiprocess extensions}) are supported, actions
 can be specified to match all threads in a process by using the
 @samp{p@var{pid}.-1} form of the @var{thread-id}.  An action with no
-@var{thread-id} is called the default action and matches all threads.
-Specifying multiple default actions is an error; specifying no actions
-is also an error.
+@var{thread-id} matches all threads.  Specifying no actions is an
+error.
 
 Currently supported actions are: