From: jose.marchesi@oracle.com (Jose E. Marchesi)
To: gdb@sourceware.org
Subject: Re: [PATCH V3 1/9] Adapt `info probes' to support printing probes of different types.
Date: Tue, 28 Oct 2014 14:06:00 -0000 [thread overview]
Message-ID: <87zjcgwafp.fsf@oracle.com> (raw)
In-Reply-To: <1414504151-31155-2-git-send-email-jose.marchesi@oracle.com> (Jose E. Marchesi's message of "Tue, 28 Oct 2014 14:49:03 +0100")
I mistyped the mailing list name while git-send-emailing. I resent the
series to gdb-patches@.
Sorry for the noise pals! :)
next prev parent reply other threads:[~2014-10-28 14:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 13:44 [PATCH V3 0/9] Add support for DTrace USDT probes to gdb Jose E. Marchesi
2014-10-28 13:44 ` [PATCH V3 1/9] Adapt `info probes' to support printing probes of different types Jose E. Marchesi
2014-10-28 14:06 ` Jose E. Marchesi [this message]
2014-10-28 13:44 ` [PATCH V3 2/9] Move `compute_probe_arg' and `compile_probe_arg' to probe.c Jose E. Marchesi
2014-10-28 13:44 ` [PATCH V3 4/9] New gdbarch functions: dtrace_parse_probe_argument, dtrace_probe_is_enabled, dtrace_enable_probe, dtrace_disable_probe Jose E. Marchesi
2014-10-28 13:44 ` [PATCH V3 8/9] Documentation for DTrace USDT probes Jose E. Marchesi
2014-10-28 16:13 ` Eli Zaretskii
2015-02-04 16:21 ` Ed Maste
2014-10-28 13:44 ` [PATCH V3 6/9] Support for DTrace USDT probes in x86_64 targets Jose E. Marchesi
2014-10-28 13:44 ` [PATCH V3 3/9] New commands `enable probe' and `disable probe' Jose E. Marchesi
2014-10-28 16:08 ` Eli Zaretskii
2014-10-28 13:44 ` [PATCH V3 9/9] Announce the DTrace USDT probes support in NEWS Jose E. Marchesi
2014-10-28 16:13 ` Eli Zaretskii
2014-10-28 13:44 ` [PATCH V3 5/9] New probe type: DTrace USDT probes Jose E. Marchesi
2014-10-28 13:44 ` [PATCH V3 7/9] Simple testsuite for " Jose E. Marchesi
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=87zjcgwafp.fsf@oracle.com \
--to=jose.marchesi@oracle.com \
--cc=gdb@sourceware.org \
/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