From: Pedro Alves <palves@redhat.com>
To: Doug Evans <xdje42@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Allow board file to specify remotetimeout
Date: Fri, 07 Nov 2014 16:47:00 -0000 [thread overview]
Message-ID: <545CF7B0.5080200@redhat.com> (raw)
In-Reply-To: <CAP9bCMQNDir0=8fXuOc2mnhFHmwnYZH9jKHMZZjWeNm47OQPTw@mail.gmail.com>
On 11/07/2014 03:25 PM, Doug Evans wrote:
> On Fri, Nov 7, 2014 at 2:21 AM, Pedro Alves <palves@redhat.com> 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
prev parent reply other threads:[~2014-11-07 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 1:02 Doug Evans
2014-11-07 10:21 ` Pedro Alves
2014-11-07 15:25 ` Doug Evans
2014-11-07 16:47 ` Pedro Alves [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=545CF7B0.5080200@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=xdje42@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox