From: Thomas Preud'homme <thomas.preudhomme@foss.arm.com>
To: Don Breazeal <donb@codesourcery.com>
Cc: Pedro Alves <palves@redhat.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [pushed][PATCH] Fix '-data-read-memory-bytes' typo/assertion
Date: Mon, 15 Feb 2016 04:58:00 -0000 [thread overview]
Message-ID: <1763439.a8mQkaxMGn@hardin.shanghai.arm.com> (raw)
In-Reply-To: <56BCA93F.7070801@codesourcery.com>
On Thursday, February 11, 2016 07:31:11 AM Don Breazeal wrote:
>
> This is now pushed to the 7.10 branch. Sorry for the delay.
Not at all, thank you!
Best regards,
Thomas
prev parent reply other threads:[~2016-02-15 4:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 0:53 [PATCH] " Don Breazeal
2015-11-19 13:27 ` Simon Marchi
2015-11-19 23:06 ` Pedro Alves
2015-11-20 18:02 ` [pushed][PATCH] " Don Breazeal
2016-02-03 12:37 ` Thomas Preud'homme
2016-02-04 18:23 ` Don Breazeal
2016-02-04 22:55 ` Don Breazeal
2016-02-04 23:02 ` Pedro Alves
2016-02-05 3:04 ` Thomas Preud'homme
2016-02-11 15:31 ` Don Breazeal
2016-02-15 4:58 ` Thomas Preud'homme [this message]
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=1763439.a8mQkaxMGn@hardin.shanghai.arm.com \
--to=thomas.preudhomme@foss.arm.com \
--cc=donb@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--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).