Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Doug Evans <dje@google.com>
Cc: Nathan Froyd <froydnj@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] fix py-inferior.exp for remote cross-endian testing
Date: Mon, 01 Nov 2010 20:13:00 -0000	[thread overview]
Message-ID: <m3bp68ajda.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20101029201604.GA813@caradoc.them.org> (Daniel Jacobowitz's	message of "Fri, 29 Oct 2010 16:16:12 -0400")

>>>>> "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?

Tom


  reply	other threads:[~2010-11-01 20:13 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 [this message]
2010-11-03 17:24       ` Doug Evans

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=m3bp68ajda.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=dje@google.com \
    --cc=froydnj@codesourcery.com \
    --cc=gdb-patches@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