From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28360 invoked by alias); 11 Mar 2013 16:59:55 -0000 Received: (qmail 28334 invoked by uid 22791); 11 Mar 2013 16:59:53 -0000 X-SWARE-Spam-Status: No, hits=-4.3 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_YE,RCVD_IN_NIX_SPAM,SARE_SUB_OBFU_Q1,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; Mon, 11 Mar 2013 16:59:37 +0000 Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0MJI00K009E5FN00@a-mtaout20.012.net.il> for gdb-patches@sourceware.org; Mon, 11 Mar 2013 18:59:22 +0200 (IST) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MJI00K7P9UWCC90@a-mtaout20.012.net.il>; Mon, 11 Mar 2013 18:59:20 +0200 (IST) Date: Mon, 11 Mar 2013 16:59:00 -0000 From: Eli Zaretskii Subject: Re: [PATCH 2/5] Query supported notifications by qSupported In-reply-to: <513DA30D.9080905@codesourcery.com> To: Yao Qi Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <837gldx47x.fsf@gnu.org> References: <1358838232-13319-1-git-send-email-yao@codesourcery.com> <1360987214-16592-1-git-send-email-yao@codesourcery.com> <1360987214-16592-3-git-send-email-yao@codesourcery.com> <8338wwsiwk.fsf@gnu.org> <513DA30D.9080905@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-03/txt/msg00474.txt.bz2 > Date: Mon, 11 Mar 2013 17:25:33 +0800 > From: Yao Qi > CC: > > On 02/16/2013 05:32 PM, Eli Zaretskii wrote: > > See above: I think you should show here the form of the > > "notifications=" part in more detail. In particular, the fact that > > each notification is of the form NOTIFICATION.ANNEX1.ANNEX2... is > > important and should be described and the meaning of the multiple > > ANNEX parts explained. > > How about this below, > > .... supported by the > stub. Each notification in the string is composed by the name of the > notification and the annexes, if any, which are separated by periods. > > > > >> >+@item Notifications=@var{name}@r{[}.@var{annex}@r{]}@dots{}@r{[},@var{name}@r{[}.@var{annex}@r{]}@dots{}@r{]}@dots{} > >> >+@cindex notifications, in remote protocol > >> >+The remote stub supports a string of notifications. @var{name} is > >> >+the name of the notification and @var{annex} is the name of the annex, > >> >+if the notification has the annex. > > Here, too, we should say explicitly that there could be several > > @var{annex} parts separated by periods. > > and this, > > if the notification has the annex. Note that the notification may > have several annexes, so here could be several @var{annex} parts > separated by periods. Thanks, I'm happy now.