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-92-gc893ecc Date: Tue, 27 Apr 2010 16:19:00 -0000 [thread overview] Message-ID: <20100427161926.9531.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 c893eccde63065539084a68680927d2e4a11ca04 (commit) from c5bbe3735cf3bc1914b630796cf6f34230db7ae0 (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 c893eccde63065539084a68680927d2e4a11ca04 Author: David Smith <dsmith@redhat.com> Date: Tue Apr 27 11:18:58 2010 -0500 PR 11338 (partial): Used @defined in nfs.stp and general update. * tapset/nfs.stp: Large update to get working on RHEL4, f12, and rawhide. RHEL5 fails because of PR 1155 (can't find inline function arguments). with probe nfs.fop.check_flags. Removed all kernel version checks. * testsuite/buildok/nfs-detailed.stp: New detailed test of all nfs probes and convenience variables. ----------------------------------------------------------------------- Summary of changes: tapset/nfs.stp | 162 ++++++++++++++++---------- testsuite/buildok/nfs-detailed.stp | 229 ++++++++++++++++++++++++++++++++++++ 2 files changed, 329 insertions(+), 62 deletions(-) create mode 100755 testsuite/buildok/nfs-detailed.stp hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-04-27 16:19 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=20100427161926.9531.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: 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).