From: Simon Marchi <simon.marchi@ericsson.com>
To: Pedro Alves <palves@redhat.com>,
Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Joel Brobecker <brobecker@adacore.com>, <gdb-patches@sourceware.org>
Subject: Re: [testsuite 7.11] Regression for i386-biarch-core.exp and others [Re: [PATCH] Always organize test artifacts in a directory hierarchy]
Date: Mon, 15 Feb 2016 16:17:00 -0000 [thread overview]
Message-ID: <56C1F9F8.2070102@ericsson.com> (raw)
In-Reply-To: <56BE644F.9010605@redhat.com>
On 16-02-12 06:01 PM, Pedro Alves wrote:
> On 02/12/2016 09:54 PM, Simon Marchi wrote:
>
>> Hmm actually, should I push it to the 7.11 branch as well?
>
> Doesn't hurt.
>
>> Is there a special procedure, or I just cherry-pick and push?
>
> Just cherry-pick, make sure ChangeLog entry is at the top, and push.
>
> Thanks,
> Pedro Alves
Ok I have pushed it to gdb-7.11-branch.
Simon
next prev parent reply other threads:[~2016-02-15 16:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 15:52 [PATCH] Always organize test artifacts in a directory hierarchy Simon Marchi
2016-01-12 13:00 ` Pedro Alves
[not found] ` <56952A6C.8070507@ericsson.com>
2016-01-13 11:11 ` Pedro Alves
2016-01-17 6:37 ` Joel Brobecker
2016-01-20 23:29 ` Simon Marchi
2016-01-25 21:24 ` Simon Marchi
2016-01-25 21:54 ` Simon Marchi
2016-02-01 22:41 ` Simon Marchi
2016-02-07 7:10 ` Joel Brobecker
2016-02-08 19:01 ` Simon Marchi
2016-02-08 19:26 ` Simon Marchi
2016-02-11 21:22 ` [testsuite 7.11] Regression for i386-biarch-core.exp and others [Re: [PATCH] Always organize test artifacts in a directory hierarchy] Jan Kratochvil
2016-02-12 18:34 ` Simon Marchi
2016-02-12 18:41 ` Pedro Alves
2016-02-12 18:56 ` Simon Marchi
2016-02-12 21:54 ` Simon Marchi
2016-02-12 23:01 ` Pedro Alves
2016-02-15 16:17 ` Simon Marchi [this message]
2016-02-12 18:47 ` Jan Kratochvil
2016-02-12 19:38 ` Simon Marchi
2016-02-15 17:58 ` [testsuite obv+7.11] Fix more testcases with standard_output_file [Re: [testsuite 7.11] Regression for i386-biarch-core.exp and others] 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=56C1F9F8.2070102@ericsson.com \
--to=simon.marchi@ericsson.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=palves@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).