From: "Wiederhake, Tim" <tim.wiederhake@intel.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
"Metzger, Markus T" <markus.t.metzger@intel.com>,
"palves@redhat.com" <palves@redhat.com>,
"xdje42@gmail.com" <xdje42@gmail.com>
Subject: RE: [PING][PATCH v5 0/9] Python bindings for btrace recordings
Date: Fri, 10 Feb 2017 13:47:00 -0000 [thread overview]
Message-ID: <9676A094AF46E14E8265E7A3F4CCE9AF93FB34@irsmsx105.ger.corp.intel.com> (raw)
In-Reply-To: <8337fm41bv.fsf@gnu.org>
Hi Eli,
>>> OK with those nits fixed.
Yes, you already approved the documentation.
Thanks,
Tim
> -----Original Message-----
> From: gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] On Behalf Of Eli Zaretskii
> Sent: Friday, February 10, 2017 2:34 PM
> To: Wiederhake, Tim <tim.wiederhake@intel.com>
> Cc: gdb-patches@sourceware.org; Metzger, Markus T
> <markus.t.metzger@intel.com>; palves@redhat.com; xdje42@gmail.com
> Subject: Re: [PING][PATCH v5 0/9] Python bindings for btrace recordings
>
> > From: "Wiederhake, Tim" <tim.wiederhake@intel.com>
> > CC: "Metzger, Markus T" <markus.t.metzger@intel.com>,
> "palves@redhat.com" <palves@redhat.com>, "xdje42@gmail.com"
> <xdje42@gmail.com>
> > Date: Fri, 10 Feb 2017 12:17:25 +0000
> >
> > Ping:
> > https://sourceware.org/ml/gdb-patches/2017-01/msg00616.html
>
> The documentation parts were already approved, right?
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
prev parent reply other threads:[~2017-02-10 13:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 12:17 Wiederhake, Tim
2017-02-10 13:34 ` Eli Zaretskii
2017-02-10 13:47 ` Wiederhake, Tim [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=9676A094AF46E14E8265E7A3F4CCE9AF93FB34@irsmsx105.ger.corp.intel.com \
--to=tim.wiederhake@intel.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.com \
--cc=palves@redhat.com \
--cc=xdje42@gmail.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