From: Luis Machado <lgustavo@codesourcery.com>
To: Pedro Alves <alves.ped@gmail.com>
Cc: Markus T Metzger <markus.t.metzger@intel.com>,
GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix more cases of improper test names
Date: Fri, 09 Dec 2016 23:21:00 -0000 [thread overview]
Message-ID: <425375a2-c3e0-50a5-8a55-33bed3a6cca4@codesourcery.com> (raw)
In-Reply-To: <CAJvqv7M2NpW0wWQvkZfRSNoohKts4g6by5zmBbYo_TdnPJg6og@mail.gmail.com>
On 12/09/2016 04:10 PM, Pedro Alves wrote:
> Em 09/12/2016 21:58, "Luis Machado" <lgustavo@codesourcery.com
> <mailto:lgustavo@codesourcery.com>> escreveu:
>>
>> I noticed more occurrences of improper test names. The rather
> mechanical, tedious and large patch below addresses, hopefully, most of
> the leftover cases.
>>
>> As usual, another pair of eyes is welcome to check if i missed
> something or did an invalid substitution. I anticipate it is going to be
> equally tedious to review this. :-)
>>
>> This patch also fixes the prepare_for_testing calls to pass proper
> test names.
>>
>> Also, since it is quite a big patch, gdb-patches@... rejected the
> message (more than 400K). Not ideal, but a tarball is attached.
>>
>
> Can you push it as a user branch?
>
Yes. Just need to figure out the proper way to do it (i suppose it is
documented somewhere).
Are you proposing it simply for review purposes or to be used for
further testsuite-related changes?
next prev parent reply other threads:[~2016-12-09 23:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-09 21:58 Luis Machado
[not found] ` <CAJvqv7M2NpW0wWQvkZfRSNoohKts4g6by5zmBbYo_TdnPJg6og@mail.gmail.com>
2016-12-09 23:21 ` Luis Machado [this message]
2016-12-12 14:02 ` Pedro Alves
2016-12-23 16:57 ` Luis Machado
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=425375a2-c3e0-50a5-8a55-33bed3a6cca4@codesourcery.com \
--to=lgustavo@codesourcery.com \
--cc=alves.ped@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.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