Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Andreas Arnez <arnez@linux.vnet.ibm.com>
Cc: gdb-patches@sourceware.org, Ulrich Weigand <uweigand@de.ibm.com>,
	       Yao Qi <qiyaoltc@gmail.com>
Subject: Re: [PING][PATCH] gnu_vector.exp: Avoid some more known FAILs
Date: Thu, 13 Aug 2015 15:59:00 -0000	[thread overview]
Message-ID: <55CCBED6.8080209@redhat.com> (raw)
In-Reply-To: <87r3n76vf6.fsf@br87z6lw.de.ibm.com>

On 08/13/2015 04:49 PM, Andreas Arnez wrote:

> Right, that would be an option.  After thinking about this a bit I
> slightly prefer to go even one step further, like in the approach below.
> In my view, it more clearly separates the steps and is more easily
> extensible at the end.  But maybe I've been thinking about this too much
> already ;-)
> 

:-)

> OK with this change?

LGTM.

Thanks,
Pedro Alves


      reply	other threads:[~2015-08-13 15:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-11 17:27 Andreas Arnez
2015-08-12 11:05 ` Pedro Alves
2015-08-13 15:49   ` Andreas Arnez
2015-08-13 15:59     ` 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=55CCBED6.8080209@redhat.com \
    --to=palves@redhat.com \
    --cc=arnez@linux.vnet.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=qiyaoltc@gmail.com \
    --cc=uweigand@de.ibm.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