[PATCH 1/5] Add annex in a async remote notification.

[Eli Zaretskii]

> From: Yao Qi <yao@codesourcery.com>
> Date: Tue, 22 Jan 2013 15:03:48 +0800
> 
> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -38604,13 +38604,15 @@ transmit notifications without fear of confusing older clients.  There
>  are no notifications defined for @value{GDBN} to send at the moment, but we
>  assume that most older stubs would ignore them, as well.)
>  
> -Each notification is comprised of three parts:
> +Each notification is comprised of four parts:
>  @table @samp
> -@item @var{name}:@var{event}
> +@item @var{name}[:@var{annex}]:@var{event}

Is it a good idea to have the optional part in the middle?  If there
are MI clients out there that support the previous form, they might
now confuse ANNEX to be an EVENT.

The documentation patch in this changeset is OK with me.