From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11452 invoked by alias); 7 Nov 2014 16:47:50 -0000 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 Received: (qmail 11442 invoked by uid 89); 7 Nov 2014 16:47:49 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Fri, 07 Nov 2014 16:47:48 +0000 Received: from int-mx13.intmail.prod.int.phx2.redhat.com (int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id sA7Glk6d028882 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Fri, 7 Nov 2014 11:47:46 -0500 Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx13.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id sA7GlihK018232; Fri, 7 Nov 2014 11:47:45 -0500 Message-ID: <545CF7B0.5080200@redhat.com> Date: Fri, 07 Nov 2014 16:47:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 MIME-Version: 1.0 To: Doug Evans CC: "gdb-patches@sourceware.org" Subject: Re: [PATCH] Allow board file to specify remotetimeout References: <545C9D31.2020305@redhat.com> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2014-11/txt/msg00141.txt.bz2 On 11/07/2014 03:25 PM, Doug Evans wrote: > On Fri, Nov 7, 2014 at 2:21 AM, Pedro Alves wrote: >> Is there an advantage to this method? > > Yeah, it's documented in testsuite/README so I'll find it next time. 1/2 :-) > :-) > I'd long since forgotten about the wiki page. > Having both places being reasonably large, and neither having a reference > to the other, is unfortunate. > [The README mentions the wiki, but without an explicit link > it's not that helpful.] > > I'd be happy with gutting testsuite/README and just mentioning the wiki url. > Thoughts? I ( still [1] ) prefer having the testsuite/README file in the tree documenting the variables that the testsuite supports, because those are tied to the specific GDB version in the tree, while the (whole) wiki doesn't really distinguish that. IMO, the wiki serves best for "recipes" and tips. It looks like testsuite/README doesn't document GDBFLAGS though. How about we fix that, and use 'set GDBFLAGS "-l 15"' as the example? I think the "Writing Tests" section of README could/should be moved to the wiki, though, e.g., to the GDBTestcaseCookbook page. [1] https://sourceware.org/ml/gdb-patches/2013-09/msg00192.html Thanks, Pedro Alves