public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: fche@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.1-241-g95ef3b3
Date: Thu, 18 Mar 2010 12:06:00 -0000	[thread overview]
Message-ID: <20100318120602.22923.qmail@sourceware.org> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "systemtap: system-wide probe/trace tool".

The branch, master has been updated
       via  95ef3b3011e48bc1a5775c320d3bbc7b84853512 (commit)
      from  654979ee0fc8d47bfd1680bc9e4c42ab2da78846 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 95ef3b3011e48bc1a5775c320d3bbc7b84853512
Author: Frank Ch. Eigler <fche@elastic.org>
Date:   Thu Mar 18 08:04:21 2010 -0400

    PR909: switch to tapset-based attr/type resolution
    
    * tapset/perf.stp: New file.
    * tapset-perfmon.cxx (perf_derived_probe): Drop event_name field throughout.
      Listen to type(N).config(M) instead.

-----------------------------------------------------------------------

Summary of changes:
 tapset-perfmon.cxx |  101 +++++++++++++---------------------------------------
 tapset/perf.stp    |   29 +++++++++++++++
 2 files changed, 54 insertions(+), 76 deletions(-)
 create mode 100644 tapset/perf.stp


hooks/post-receive
--
systemtap: system-wide probe/trace tool


                 reply	other threads:[~2010-03-18 12:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20100318120602.22923.qmail@sourceware.org \
    --to=fche@sourceware.org \
    --cc=systemtap-cvs@sourceware.org \
    --cc=systemtap@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).