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.7-94-g7da7727
Date: Fri, 08 May 2009 20:07:00 -0000	[thread overview]
Message-ID: <20090508200717.9585.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  7da77276c8a703a4dab1ed242801f3afd38864ea (commit)
      from  b77eb29cbffe96e7fb7db4513b4b8610d134141f (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 7da77276c8a703a4dab1ed242801f3afd38864ea
Author: Josh Stone <jistone@redhat.com>
Date:   Fri May 8 12:40:43 2009 -0700

    Simplify buildok/context_test.stp
    
    The test was using optional probes on uptime_read_proc, which doesn't
    exist anymore on 2.6.30.  The problem is that when those optional probes
    are skipped, the test doesn't really do anything.
    
    For a buildok test of the context functions, the actual probe point
    doesn't matter, so I've changed it to just a begin probe that calls all
    of the functions.

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

Summary of changes:
 testsuite/buildok/context_test.stp |   21 +--------------------
 1 files changed, 1 insertions(+), 20 deletions(-)


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


                 reply	other threads:[~2009-05-08 20:07 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=20090508200717.9585.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).