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-133-gd950c89
Date: Mon, 10 May 2010 20:32:00 -0000 [thread overview]
Message-ID: <20100510203257.13135.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 d950c89398e9088b789d5a44e737ffb55c3b1689 (commit)
from a8138db70b64ef03a773ff6f5de77af50465e537 (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 d950c89398e9088b789d5a44e737ffb55c3b1689
Author: David Smith <dsmith@redhat.com>
Date: Mon May 10 15:32:28 2010 -0500
Updated ioscheduler.stp and tests.
* tapset/ioscheduler.stp: Large update to get working on RHEL4, RHEL5,
RHEL6(beta), f11, f12, and rawhide.
* testsuite/buildok/ioscheduler-all-probes.stp: New test.
* testsuite/buildok/ioscheduler-detailed.stp: New detailed test of all
ioscheduler probes and convenience variables.
* testsuite/buildok/ioscheduler.stp: Deleted, since no longer needed with
the addition of ioscheduler-detailed.stp.
-----------------------------------------------------------------------
Summary of changes:
tapset/ioscheduler.stp | 181 +++++++++++++++-----------
testsuite/buildok/ioscheduler-all-probes.stp | 7 +
testsuite/buildok/ioscheduler-detailed.stp | 42 ++++++
testsuite/buildok/ioscheduler.stp | 21 ---
4 files changed, 157 insertions(+), 94 deletions(-)
create mode 100644 testsuite/buildok/ioscheduler-all-probes.stp
create mode 100755 testsuite/buildok/ioscheduler-detailed.stp
delete mode 100755 testsuite/buildok/ioscheduler.stp
hooks/post-receive
--
systemtap: system-wide probe/trace tool
reply other threads:[~2010-05-10 20:32 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=20100510203257.13135.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).