From: Doug Evans <dje@google.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Nathan Froyd <froydnj@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] fix py-inferior.exp for remote cross-endian testing
Date: Wed, 03 Nov 2010 17:24:00 -0000 [thread overview]
Message-ID: <AANLkTik7Mb7i-EzRdwXoxtkZwNHELYbKq9AixW5ynunt@mail.gmail.com> (raw)
In-Reply-To: <m3bp68ajda.fsf@fleche.redhat.com>
On Mon, Nov 1, 2010 at 1:17 PM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "Daniel" == Daniel Jacobowitz <dan@codesourcery.com> writes:
>
> Daniel> So that's at least one obvious bug ("" vs "auto"), and one more
> Daniel> complex bug (what should it return for auto?). I'm inclined to say
> Daniel> that it should return auto, and there should be some other way to find
> Daniel> out "auto what?"; OTOH, it's a general problem with parameters...
>
> Could you file a bug report for this?
http://sourceware.org/bugzilla/show_bug.cgi?id=12188
prev parent reply other threads:[~2010-11-03 17:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-29 19:20 Nathan Froyd
2010-10-29 19:49 ` Doug Evans
2010-10-29 20:16 ` Daniel Jacobowitz
2010-11-01 20:13 ` Tom Tromey
2010-11-03 17:24 ` Doug Evans [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=AANLkTik7Mb7i-EzRdwXoxtkZwNHELYbKq9AixW5ynunt@mail.gmail.com \
--to=dje@google.com \
--cc=froydnj@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.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