Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Wiederhake, Tim" <tim.wiederhake@intel.com>
To: Doug Evans <xdje42@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	"Metzger, Markus T" <markus.t.metzger@intel.com>,
	"palves@redhat.com"	<palves@redhat.com>
Subject: RE: [PATCH v6 0/9] Python bindings for btrace recordings
Date: Tue, 14 Feb 2017 10:20:00 -0000	[thread overview]
Message-ID: <9676A094AF46E14E8265E7A3F4CCE9AF94021F@irsmsx105.ger.corp.intel.com> (raw)
In-Reply-To: <m3d1emovqf.fsf@sspiff.org>

Hi all,

> > Is this good to go?
> LGTM

... And in return I made a mess. What should have been a "git push --dry-run" to prepare for pushing this, ended up as an actual push. The commits now miss the actual ChangeLog entries and contain some "Change-Id" lines. Before I start fiddeling and probably make things worse, could you tell me how to properly resolve this?

Thanks,
Tim

> -----Original Message-----
> From: Doug Evans [mailto:xdje42@gmail.com]
> Sent: Monday, February 13, 2017 6:18 PM
> To: Wiederhake, Tim <tim.wiederhake@intel.com>
> Cc: gdb-patches@sourceware.org; Metzger, Markus T
> <markus.t.metzger@intel.com>; palves@redhat.com
> Subject: Re: [PATCH v6 0/9] Python bindings for btrace recordings
> 
> Tim Wiederhake <tim.wiederhake@intel.com> writes:
> > Hello everyone!
> >
> > This patch series adds Python bindings for btrace recordings.
> >
> > V1 of this series can be found here:
> > https://sourceware.org/ml/gdb-patches/2016-10/msg00733.html
> >
> > V2 of this series can be found here:
> > https://sourceware.org/ml/gdb-patches/2016-11/msg00084.html
> >
> > V3 of this series can be found here:
> > https://sourceware.org/ml/gdb-patches/2016-11/msg00605.html
> >
> > V4 of this series can be found here:
> > https://sourceware.org/ml/gdb-patches/2017-01/msg00044.html
> >
> > V5 of this series can be found here:
> > https://sourceware.org/ml/gdb-patches/2017-01/msg00616.html
> >
> > Changes from V5:
> >  - Skip gdb.python/py-record-full.exp if recording is not supported.
> >  - s/symbol/SAL/ in comment in py-record-btrace.c.
> >  - Replaced mem_fileopen by string_file in py-record-btrace.c.
> >  - Simplified btpy_list_count and added comment in py-record-btrace.c.
> >  - Removed unused variable in recpy_bt_goto (leftover from previous
> refactoring)
> >    in py-record-btrace.c.
> >  - Moved opening curly braces to new line in py-record-btrace.c.
> >
> > The documentation parts are already approved by Eli.
> >
> > Is this good to go?
> 
> LGTM
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


  reply	other threads:[~2017-02-14 10:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-13 12:38 Tim Wiederhake
2017-02-13 12:38 ` [PATCH v6 6/9] python: Create Python bindings for record history Tim Wiederhake
2017-02-13 12:38 ` [PATCH v6 3/9] btrace: Use binary search to find instruction Tim Wiederhake
2017-02-13 12:38 ` [PATCH v6 1/9] btrace: Count gaps as one instruction explicitly Tim Wiederhake
2017-02-13 12:38 ` [PATCH v6 2/9] btrace: Export btrace_decode_error function Tim Wiederhake
2017-02-13 12:38 ` [PATCH v6 4/9] Add record_start and record_stop functions Tim Wiederhake
2017-02-13 12:38 ` [PATCH v6 5/9] Add method to query current recording method to target_ops Tim Wiederhake
2017-02-13 12:38 ` [PATCH v6 9/9] Add documentation for new record Python bindings Tim Wiederhake
2017-02-13 14:48   ` Eli Zaretskii
2017-03-03 11:10   ` Yao Qi
2017-03-06  8:56     ` Wiederhake, Tim
2017-03-07 11:53       ` Yao Qi
     [not found]         ` <9676A094AF46E14E8265E7A3F4CCE9AF942A2E@irsmsx105.ger.corp.intel.com>
2017-03-17 16:50           ` Yao Qi
     [not found] ` <1486989450-11313-8-git-send-email-tim.wiederhake@intel.com>
2017-02-13 17:03   ` [PATCH v6 7/9] python: Implement btrace Python bindings for record history Doug Evans
2017-02-13 17:12   ` Doug Evans
     [not found] ` <1486989450-11313-9-git-send-email-tim.wiederhake@intel.com>
2017-02-13 17:17   ` [PATCH v6 8/9] python: Add tests for record Python bindings Doug Evans
2017-02-13 17:18 ` [PATCH v6 0/9] Python bindings for btrace recordings Doug Evans
2017-02-14 10:20   ` Wiederhake, Tim [this message]
2017-02-14 16:22     ` Doug Evans
2017-02-15  7:35       ` Wiederhake, Tim

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=9676A094AF46E14E8265E7A3F4CCE9AF94021F@irsmsx105.ger.corp.intel.com \
    --to=tim.wiederhake@intel.com \
    --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