From: Eli Zaretskii <eliz@gnu.org>
To: "Jose E. Marchesi" <jose.marchesi@oracle.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [COMMITTED V5 9/9] Announce the DTrace USDT probes support in NEWS.
Date: Tue, 17 Feb 2015 16:31:00 -0000 [thread overview]
Message-ID: <83sie45wkt.fsf@gnu.org> (raw)
In-Reply-To: <1424189897-32457-10-git-send-email-jose.marchesi@oracle.com>
> From: "Jose E. Marchesi" <jose.marchesi@oracle.com>
> Date: Tue, 17 Feb 2015 17:18:17 +0100
>
> This patch simply adds a small entry to `Changes since GDB 7.8' announcing the
> support for dtrace probes.
>
> gdb/ChangeLog:
>
> 2015-02-17 Jose E. Marchesi <jose.marchesi@oracle.com>
>
> * NEWS: Announce the support for DTrace SDT probes.
Fine with me, thanks.
next prev parent reply other threads:[~2015-02-17 16:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-17 16:12 [COMMITTED V5 0/9] Add support for DTrace USDT probes to gdb Jose E. Marchesi
2015-02-17 16:12 ` [COMMITTED V5 3/9] New commands `enable probe' and `disable probe' Jose E. Marchesi
2015-02-17 16:12 ` [COMMITTED V5 2/9] Move `compute_probe_arg' and `compile_probe_arg' to probe.c Jose E. Marchesi
2015-02-17 16:12 ` [COMMITTED V5 1/9] Adapt `info probes' to support printing probes of different types Jose E. Marchesi
2015-02-17 16:12 ` [COMMITTED V5 4/9] New gdbarch functions: dtrace_parse_probe_argument, dtrace_probe_is_enabled, dtrace_enable_probe, dtrace_disable_probe Jose E. Marchesi
2015-02-17 16:13 ` [COMMITTED V5 5/9] New probe type: DTrace USDT probes Jose E. Marchesi
2015-02-17 16:13 ` [COMMITTED V5 7/9] Simple testsuite for " Jose E. Marchesi
2015-02-17 16:13 ` [COMMITTED V5 6/9] Support for DTrace USDT probes in x86_64 targets Jose E. Marchesi
2015-02-17 16:13 ` [COMMITTED V5 8/9] Documentation for DTrace USDT probes Jose E. Marchesi
2015-02-17 16:13 ` [COMMITTED V5 9/9] Announce the DTrace USDT probes support in NEWS Jose E. Marchesi
2015-02-17 16:31 ` Eli Zaretskii [this message]
2015-02-17 16:45 ` 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=83sie45wkt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jose.marchesi@oracle.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