From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20668 invoked by alias); 22 Jan 2013 08:06:00 -0000 Received: (qmail 20654 invoked by uid 22791); 22 Jan 2013 08:05:59 -0000 X-SWARE-Spam-Status: No, hits=-4.5 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,RCVD_IN_NIX_SPAM,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout20.012.net.il (HELO mtaout20.012.net.il) (80.179.55.166) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 22 Jan 2013 08:05:52 +0000 Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0MH000A00P3QS600@a-mtaout20.012.net.il> for gdb-patches@sourceware.org; Tue, 22 Jan 2013 10:05:12 +0200 (IST) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MH000A54P4NPW30@a-mtaout20.012.net.il>; Tue, 22 Jan 2013 10:05:12 +0200 (IST) Date: Tue, 22 Jan 2013 08:06:00 -0000 From: Eli Zaretskii Subject: Re: [PATCH 1/5] Add annex in a async remote notification. In-reply-to: <1358838232-13319-2-git-send-email-yao@codesourcery.com> To: Yao Qi Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83fw1tod6e.fsf@gnu.org> References: <1358838232-13319-1-git-send-email-yao@codesourcery.com> <1358838232-13319-2-git-send-email-yao@codesourcery.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2013-01/txt/msg00512.txt.bz2 > From: Yao Qi > 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.