public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: dsmith@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.2-66-g93a7a5b
Date: Tue, 20 Apr 2010 18:11:00 -0000	[thread overview]
Message-ID: <20100420181129.28883.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  93a7a5bf8265ce7c1425ca77e3a68896a659cbcd (commit)
      from  85194550f80d702810cf7f82905e8e919e17ae99 (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 93a7a5bf8265ce7c1425ca77e3a68896a659cbcd
Author: David Smith <dsmith@redhat.com>
Date:   Tue Apr 20 13:10:46 2010 -0500

    Fixed PR 3833 by updating nfs_proc.stp (and removing kernel version checks).
    
    * tapset/nfs_proc.stp: Large update to get working on RHEL4, RHEL5, f12,
      and rawhide.
    * testsuite/buildok/nfs_proc-detailed.stp: New detailed test of all
      nfs_proc probes and convenience variables.

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

Summary of changes:
 tapset/nfs_proc.stp                     |  281 +++++++++++++++++--------------
 testsuite/buildok/nfs_proc-detailed.stp |  148 ++++++++++++++++
 2 files changed, 302 insertions(+), 127 deletions(-)
 create mode 100755 testsuite/buildok/nfs_proc-detailed.stp


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


                 reply	other threads:[~2010-04-20 18:11 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=20100420181129.28883.qmail@sourceware.org \
    --to=dsmith@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).