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.6-236-ge86f32e Date: Tue, 20 Sep 2011 14:51:00 -0000 [thread overview] Message-ID: <20110920145147.10760.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 e86f32ee4ed78c9092d27c66627fdaeb589c02ff (commit) from 0f79a69995d11865cd6231ee15170ab82453426f (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 e86f32ee4ed78c9092d27c66627fdaeb589c02ff Author: Frank Ch. Eigler <fche@redhat.com> Date: Tue Sep 20 10:49:41 2011 -0400 BZ732346 vs PR12729: don't print make failure messages for bad tracepoints Having buggy/incomplete kernel tracepoint headers is routine, but PR12729 started relaying make/gcc complaints about them to the user. That's unkind. * buildrun.cxx (make_tracequery): Run "make -i" instead of "make" for tracequery jobs. ----------------------------------------------------------------------- Summary of changes: buildrun.cxx | 7 ++++--- 1 files changed, 4 insertions(+), 3 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-09-20 14:51 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=20110920145147.10760.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).