From: Eli Zaretskii <eliz@gnu.org>
To: "Metzger, Markus T" <markus.t.metzger@intel.com>
Cc: palves@redhat.com, gdb-patches@sourceware.org
Subject: Re: [PATCH v2 1/3] btrace: control memory access during replay
Date: Wed, 21 May 2014 15:12:00 -0000 [thread overview]
Message-ID: <83iooznp1v.fsf@gnu.org> (raw)
In-Reply-To: <A78C989F6D9628469189715575E55B230C16FA13@IRSMSX104.ger.corp.intel.com>
> From: "Metzger, Markus T" <markus.t.metzger@intel.com>
> CC: "palves@redhat.com" <palves@redhat.com>, "gdb-patches@sourceware.org"
> <gdb-patches@sourceware.org>
> Date: Wed, 21 May 2014 06:09:59 +0000
>
> > > +Control the behavior of the @code{btrace} recording method when
> >
> > Please be consistent about the markup of "btrace": either plain text
> > or @code{}; pick one and use it everywhere.
>
> I'm using @code{btrace} when referring to the record target or recording
> method, and I'm using just btrace when referring to a GDB command.
> I hope that's OK.
GDB commands also get the @code markup.
> I fixed one inconsistency I added with this patch.
I hope that was with "btrace record target".
next prev parent reply other threads:[~2014-05-21 15:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 12:01 Markus Metzger
2014-05-20 12:00 ` [PATCH v2 2/3] test, gcore: move capture_command_output into lib/gdb.exp Markus Metzger
2014-05-20 12:27 ` Pedro Alves
2014-05-20 12:00 ` [PATCH v2 3/3] btrace, vdso: add vdso target sections Markus Metzger
2014-05-20 13:16 ` Pedro Alves
2014-05-20 14:10 ` Metzger, Markus T
2014-05-20 12:26 ` [PATCH v2 1/3] btrace: control memory access during replay Pedro Alves
2014-05-20 16:12 ` Eli Zaretskii
2014-05-21 6:10 ` Metzger, Markus T
2014-05-21 15:12 ` Eli Zaretskii [this message]
2014-05-22 6:12 ` Metzger, Markus T
2014-05-22 14:58 ` Eli Zaretskii
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=83iooznp1v.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.com \
--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