From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org, gcc-patches@gcc.gnu.org
Subject: Re: [patch] Fix *.log tests merged output containing "==="
Date: Mon, 22 Mar 2010 19:40:00 -0000 [thread overview]
Message-ID: <m38w9kqh6e.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100308231019.GA19312@host0.dyn.jankratochvil.net> (Jan Kratochvil's message of "Tue, 9 Mar 2010 00:10:19 +0100")
>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
Jan> while *.sum files were OK the *.log files sometimes miss the
Jan> content present in *.sum results. For example
Jan> gdb.base/bitfields.exp output was missing while
Jan> gdb.base/bitfields.exp output was present.
Jan> OK to check-in? (GCC + GDB approval requested)
This is ok for gdb as well.
Thanks.
Tom
next prev parent reply other threads:[~2010-03-22 19:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 23:10 Jan Kratochvil
2010-03-22 19:40 ` Tom Tromey [this message]
2010-03-22 20:24 ` Jan Kratochvil
2010-03-22 20:26 ` Tom Tromey
2010-03-22 20:41 ` 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=m38w9kqh6e.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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