public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: mark@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.6-264-ga73b500 Date: Fri, 30 Sep 2011 14:07:00 -0000 [thread overview] Message-ID: <20110930140706.6155.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 a73b50011cb4551eee930aef170179b6a4a74e0c (commit) from 6ad1ef619bfd78c00c3fbe77376ce0ffbfc49e0d (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 a73b50011cb4551eee930aef170179b6a4a74e0c Author: Mark Wielaard <mjw@redhat.com> Date: Fri Sep 30 15:57:43 2011 +0200 Check module was actually created in tracepoint_builder. Commit e86f32 added -i to the make invocation for tracequery jobs. This means make would succeed even if there were errors. So it was possible that tracequery_ko didn't actually exist. Leading to spurious warnings about copying non-existing files into the cache when used. ----------------------------------------------------------------------- Summary of changes: tapsets.cxx | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-09-30 14:07 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=20110930140706.6155.qmail@sourceware.org \ --to=mark@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).