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-659-g7288f08 Date: Mon, 02 Jan 2012 21:52:00 -0000 [thread overview] Message-ID: <20120102215221.1513.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 7288f08ed046ada8ccc67bff25b167b714753664 (commit) via ae5e0bbb5ece659773fc63b4e332630895eb74c9 (commit) from e3f1dffecc903e49debec819459f0de1ba20b6e6 (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 7288f08ed046ada8ccc67bff25b167b714753664 Author: Frank Ch. Eigler <fche@redhat.com> Date: Fri Dec 30 11:53:52 2011 -0500 testsuite: unload uprobes at start of run * testsuite/lib/systemtap.exp (setup_systemtap_environment): In case we have an old one still sitting around, zap it, to force its rebuild. commit ae5e0bbb5ece659773fc63b4e332630895eb74c9 Author: Frank Ch. Eigler <fche@redhat.com> Date: Fri Dec 30 11:52:45 2011 -0500 when building uprobes.ko, don't suppress make stderr * buildrun.cxx (make_uprobes): Build with same quietness policy as base systemtap module, rather than -vvvv policy for tracepoint/query test modules. ----------------------------------------------------------------------- Summary of changes: buildrun.cxx | 3 +-- testsuite/lib/systemtap.exp | 3 +++ 2 files changed, 4 insertions(+), 2 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2012-01-02 21:52 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=20120102215221.1513.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).