From: Pedro Alves <palves@redhat.com>
To: Siddhesh Poyarekar <siddhesh@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix gdb.base/auxv and gdb.base/cond-eval-mode test cases
Date: Fri, 16 Mar 2012 15:50:00 -0000 [thread overview]
Message-ID: <4F63613A.4080501@redhat.com> (raw)
In-Reply-To: <20120316143002.GB22830@spoyarek.pnq.redhat.com>
On 03/16/2012 02:30 PM, Siddhesh Poyarekar wrote:
...
> Further, the
> cond-eval-mode test looks for the wrong message, again resulting in a
> spurious test failure.
...
> 2012-03-16 Siddhesh Poyarekar <siddhesh@redhat.com>
>
...
> * gdb.base/cond-eval-mode.exp: Fix the anticipated warning
> string
Please always send separate logical changes as separate emails, each with
its own subject line, description and patch. This part is obvious and
could have gone in immediately.
--
Pedro Alves
next prev parent reply other threads:[~2012-03-16 15:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 14:29 Siddhesh Poyarekar
2012-03-16 15:50 ` Pedro Alves [this message]
2012-03-17 7:27 ` Siddhesh Poyarekar
2012-03-19 9:35 ` [commit] " Jan Kratochvil
2012-03-17 7:37 ` [PATCH] Fix core dump test case failure with a ulimit check in gdb.base/auxv.exp Siddhesh Poyarekar
2012-03-19 9:43 ` Jan Kratochvil
2012-03-19 15:57 ` Siddhesh Poyarekar
2012-03-19 16:13 ` Jan Kratochvil
2012-03-19 16:39 ` Siddhesh Poyarekar
2012-03-19 18:40 ` [commit] " Jan Kratochvil
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=4F63613A.4080501@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=siddhesh@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