From: Pedro Alves <palves@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [commit] [testsuite patch] Fix false FAILs on too long base directory
Date: Tue, 12 Jan 2016 01:35:00 -0000 [thread overview]
Message-ID: <5694586A.2050504@redhat.com> (raw)
In-Reply-To: <20160111211343.GA7327@host1.jankratochvil.net>
On 01/11/2016 09:13 PM, Jan Kratochvil wrote:
> On Mon, 11 Jan 2016 15:34:15 +0100, Pedro Alves wrote:
>> OK.
>
> Checked in:
> c0ecb95f3dc0c3e8d1545f0a37c0c3e537e1ea96
This actually reverted the whole
"List inferiors/threads/pspaces in ascending order"
commit (7e0aa6aa9983). :-P I've reapplied it now.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-01-12 1:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 22:30 Jan Kratochvil
2016-01-11 14:34 ` Pedro Alves
2016-01-11 21:13 ` [commit] " Jan Kratochvil
2016-01-12 1:35 ` Pedro Alves [this message]
2016-01-12 3:07 ` 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=5694586A.2050504@redhat.com \
--to=palves@redhat.com \
--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