public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: srikar@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. rhel52-ga-444-g471ca45 Date: Fri, 27 Jun 2008 08:53:00 -0000 [thread overview] Message-ID: <20080627085330.23583.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 471ca45b8e46177b5ee2f1f7eb4bf7d7881793df (commit) from 93126f9efcd0511e2034a44fe8e5dfdcb80095af (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 471ca45b8e46177b5ee2f1f7eb4bf7d7881793df Author: root <root@srdronam.in.ibm.com> Date: Fri Jun 27 13:57:52 2008 +0530 This commit makes changes to the VFS tapset. The changes include deprecation of some old probe points to older versions of kernel, adding new helper C functions and probe points for the VFS subsystem. A new testcase is created for the VFS tapset which performs a compile test (i.e. up4) on the probe points to verify sanity. These details can also be found in the ChangeLog. ----------------------------------------------------------------------- Summary of changes: ChangeLog | 10 + tapset/vfs.stp | 303 +++++++++++++++++++++++- testsuite/buildok/vfs_testcase.stp | 461 ++++++++++++++++++++++++++++++++++++ 3 files changed, 768 insertions(+), 6 deletions(-) create mode 100644 testsuite/buildok/vfs_testcase.stp hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2008-06-27 8:53 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=20080627085330.23583.qmail@sourceware.org \ --to=srikar@sourceware.org \ --cc=systemtap-cvs@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: linkBe 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).