public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: jistone@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-0.9.5-204-g9ccda27 Date: Wed, 22 Apr 2009 03:09:00 -0000 [thread overview] Message-ID: <20090422030906.32325.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 9ccda279d763ef16ac20e171b3136d1741d07014 (commit) via 43e8f8d02ab60eb24b6d8cba1105ef92a080e5f1 (commit) from 8b31197b0c87947c37061c3a5493daa4e6927d56 (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 9ccda279d763ef16ac20e171b3136d1741d07014 Author: Josh Stone <jistone@redhat.com> Date: Tue Apr 21 19:57:59 2009 -0700 [tracepoints] Resolve implicit trace_X use Some of the tracepoints are actually being called in inlines in the common headers (e.g. trace_kmalloc), which is causing errors about implicit function declarations. We don't care about ever running the code in the tracequery module, so I'm just suppressing that error. commit 43e8f8d02ab60eb24b6d8cba1105ef92a080e5f1 Author: Josh Stone <jistone@redhat.com> Date: Tue Apr 21 19:55:47 2009 -0700 [tracepoints] Don't use TRACE_HEADER_MULTI_READ At one point that macro was needed to get all of the tracepoints on the tip tree, but now it's causing us to get duplicate stapprobe_X definitions. AFAICS, we're now getting all tracepoints even without MULTI_READ, so I'm pulling that workaround out. ----------------------------------------------------------------------- Summary of changes: buildrun.cxx | 7 ++----- 1 files changed, 2 insertions(+), 5 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2009-04-22 3:09 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=20090422030906.32325.qmail@sourceware.org \ --to=jistone@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).