Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: Nathan Froyd <froydnj@codesourcery.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
	 "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Question re: testsuite, "isnative", "is_remote" etc.
Date: Fri, 14 Jan 2011 01:26:00 -0000	[thread overview]
Message-ID: <4D2FA63B.4000000@vmware.com> (raw)
In-Reply-To: <20110113210048.GV6247@codesourcery.com>

Nathan Froyd wrote:
> On Thu, Jan 13, 2011 at 12:59:17PM -0800, Michael Snyder wrote:
>> The thing is, the situation is the same as now.  We either have to
>> put "isremote" in our board file (as now), or replace it by putting
>> "use_gdb_stub" in our board file.
>>
>> A lot of changed tests for, as I see it, no benefit.
> 
> You'll endlessly modify comments and reformat strings, but you won't run
> a one-liner perl script over the testsuite? ;)

It's exchanging one user-settable flag for another.  I don't see the point.

Besides, I don't do perl.   ;-)


  reply	other threads:[~2011-01-14  1:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-12 23:14 Michael Snyder
2011-01-12 23:19 ` Joel Brobecker
2011-01-12 23:20 ` Joel Brobecker
2011-01-12 23:23   ` Michael Snyder
     [not found]     ` <AANLkTi=R-L9-=O6cWW_aTBAoZFmmo_MMB57g2HZy85je@mail.gmail.com>
2011-01-13 18:27       ` Michael Snyder
2011-01-13 18:37         ` Joel Brobecker
2011-01-13 18:51           ` Michael Snyder
2011-01-13 18:40 ` Nathan Froyd
2011-01-13 19:04   ` Michael Snyder
2011-01-13 19:32     ` Joel Brobecker
2011-01-13 19:54       ` Michael Snyder
2011-01-13 20:53         ` Joel Brobecker
2011-01-13 20:59           ` Michael Snyder
2011-01-13 21:00             ` Nathan Froyd
2011-01-14  1:26               ` Michael Snyder [this message]
2011-01-13 21:27             ` Joel Brobecker
2011-01-13 21:29               ` Joel Brobecker

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=4D2FA63B.4000000@vmware.com \
    --to=msnyder@vmware.com \
    --cc=brobecker@adacore.com \
    --cc=froydnj@codesourcery.com \
    --cc=gdb@sourceware.org \
    /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