public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: jistone@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-0.9-109-g6769e48
Date: Thu, 12 Mar 2009 03:52:00 -0000	[thread overview]
Message-ID: <20090312035218.5677.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  6769e48794cfbeda3957f691077fb9d65f3e87bc (commit)
      from  139dee87b8824df4d7562a980e886a6e6f0b8308 (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 6769e48794cfbeda3957f691077fb9d65f3e87bc
Author: Josh Stone <jistone@redhat.com>
Date:   Wed Mar 11 20:30:58 2009 -0700

    Add test to compile and run all tracepoints
    
    This checks that kernel.trace("*") will compile, with all context
    variables accessed as well.  For kernels without tracepoints, it will
    just hit a "begin" and quit.
    
    This doesn't ensure that kernel.trace("*") will always find something
    when it should, though...

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

Summary of changes:
 testsuite/systemtap.base/tracepoints.exp |    3 +++
 testsuite/systemtap.base/tracepoints.stp |   23 +++++++++++++++++++++++
 2 files changed, 26 insertions(+), 0 deletions(-)
 create mode 100644 testsuite/systemtap.base/tracepoints.exp
 create mode 100644 testsuite/systemtap.base/tracepoints.stp


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


                 reply	other threads:[~2009-03-12  3:52 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=20090312035218.5677.qmail@sourceware.org \
    --to=jistone@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).