From: Simon Marchi <simon.marchi@polymtl.ca>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2] gdb: Use C++11 std::chrono
Date: Wed, 23 Nov 2016 02:57:00 -0000 [thread overview]
Message-ID: <80b4d8479ef46220a19d2ebbe5a30f5c@polymtl.ca> (raw)
In-Reply-To: <abb2778b-109c-0d09-550d-a72a79468091@redhat.com>
On 2016-11-22 21:36, Pedro Alves wrote:
> Alright. Thanks for the review!
>
> Since this adds new files to the Makefile.in lists, I'll wait
> for you to push your series in first.
Hmm weird, I thought it was pushed (and said so on the list), but I see
that it's not. Perhaps somebody managed to push a commit just before me
and I didn't notice that the push fail... I'll verify tomorrow morning
(it's on my work computer).
next prev parent reply other threads:[~2016-11-23 2:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 17:15 [PATCH] " Pedro Alves
2016-11-17 22:15 ` Simon Marchi
2016-11-23 0:59 ` [PATCH v2] " Pedro Alves
2016-11-23 2:01 ` Simon Marchi
2016-11-23 2:17 ` Pedro Alves
2016-11-23 2:27 ` Simon Marchi
2016-11-23 2:36 ` Pedro Alves
2016-11-23 2:57 ` Simon Marchi [this message]
2016-11-23 14:48 ` Simon Marchi
2016-11-23 16:02 ` Pedro Alves
2016-11-23 16:11 ` Simon Marchi
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=80b4d8479ef46220a19d2ebbe5a30f5c@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--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