From: Pedro Alves <palves@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Upload TSVs in extend-remote mode
Date: Tue, 25 Jun 2013 14:21:00 -0000 [thread overview]
Message-ID: <51C9A634.20904@redhat.com> (raw)
In-Reply-To: <51C994D7.40603@codesourcery.com>
On 06/25/2013 02:02 PM, Yao Qi wrote:
> On 06/24/2013 11:25 PM, Pedro Alves wrote:
>> update the board file. I'd suggest in the same vein, making ".*${tsv}.*"
>> less lax. Otherwise, I'm afraid this is the sort of board setting that
>> will just go silently unnoticed.
>
> I think about making the regexp less lax, but run out of ideas. Users
> can set a regexp in gdb,predefined_tsv if their targets has multiple
> predfined tsvs, for example, there are two predefined tsvs "$foo" and
> "$bar", and this line can be written in the board file,
>
> set_board_info gdb,predefined_tsv "\\\$foo.*\\\$bar"
>
> so it is hard to make ".*${tsv}.*" more strict, afaik.
Well, it'd be the board writer's responsibility to only do
that if he wanted to be lax, but I don't think this is that
important. Fine with me as is.
Thanks!
--
Pedro Alves
prev parent reply other threads:[~2013-06-25 14:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 10:40 Yao Qi
2013-06-20 18:36 ` Pedro Alves
2013-06-22 11:23 ` Yao Qi
2013-06-24 15:50 ` Pedro Alves
2013-06-25 13:57 ` Yao Qi
2013-06-25 14:21 ` 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=51C9A634.20904@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.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