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-1.1-248-gf33e915 Date: Thu, 18 Mar 2010 21:04:00 -0000 [thread overview] Message-ID: <20100318210412.9632.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 f33e91514d142459cea02bd81effb2b5dc3051ec (commit) via cc7c5c9ffb0cd9d2961ada9faa8e9f270b9e04b4 (commit) from 8496536f6ede3308e0d1cc6f1219e76ca262f1c0 (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 f33e91514d142459cea02bd81effb2b5dc3051ec Author: Frank Ch. Eigler <fche@elastic.org> Date: Thu Mar 18 17:03:48 2010 -0400 PR909: baby documentation for perf.* probes commit cc7c5c9ffb0cd9d2961ada9faa8e9f270b9e04b4 Author: Frank Ch. Eigler <fche@elastic.org> Date: Thu Mar 18 16:39:32 2010 -0400 optimizer diagnostics: identify taken branch of optimizations * elaborate.cxx (const_folder::visit_if_statement, visit_binary_expression, visit_ternary_expression): Print constant value in -vvv diagnostics. ----------------------------------------------------------------------- Summary of changes: .gitignore | 1 - NEWS | 6 +++++ elaborate.cxx | 6 ++-- man/tapset::perf.3stap | 58 ++++++++++++++++++++++++++++++++++++++++++++++++ stapprobes.3stap.in | 27 ++++++++++++++++++++++ 5 files changed, 94 insertions(+), 4 deletions(-) create mode 100644 man/tapset::perf.3stap hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-03-18 21:04 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=20100318210412.9632.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).