public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: fche@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-0.9.8-129-g665e125 Date: Wed, 08 Jul 2009 17:22:00 -0000 [thread overview] Message-ID: <20090708172253.15639.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 665e12562a4aa4f40aeeed0cfd207b49f89c9fd1 (commit) from 619d9aaf011c975159a79d34259083a596162bf1 (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 665e12562a4aa4f40aeeed0cfd207b49f89c9fd1 Author: Frank Ch. Eigler <fche@elastic.org> Date: Wed Jul 8 13:04:10 2009 -0400 PR3498 cont'd, fix wildcard module("*") probes * dwflpp.cxx (name_has_wildcard): Make static. (dwfl_report_offline_predicate): Check & adjust behavior. * dwflpp.h: Corresponding changes. * tapsets.cxx: Note that kern_dw[] keys may be wildcard strings. * testsuite/buildok/fortysix.stp: New test. ----------------------------------------------------------------------- Summary of changes: dwflpp.cxx | 44 ++++++++++++++++++++-------------------- dwflpp.h | 2 +- tapsets.cxx | 2 +- testsuite/buildok/fortysix.stp | 3 ++ 4 files changed, 27 insertions(+), 24 deletions(-) create mode 100755 testsuite/buildok/fortysix.stp hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2009-07-08 17:22 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=20090708172253.15639.qmail@sourceware.org \ --to=fche@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).