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.2-523-gec16c5a Date: Wed, 21 Jul 2010 20:42:00 -0000 [thread overview] Message-ID: <20100721204231.12682.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 ec16c5a59412e6f40c2fc7074b52c480a9372ac3 (commit) from eb8e580fd12ca2292927a0c0f045bac89b7a7e85 (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 ec16c5a59412e6f40c2fc7074b52c480a9372ac3 Author: Mark Wielaard <mjw@redhat.com> Date: Wed Jul 21 22:24:33 2010 +0200 Extend vta-test.exp testcase for PR11825 and add 32-on-64 for fun. * testsuite/systemtap.base/vta-test.c: Provide constants through struct. * testsuite/systemtap.base/vta-test.exp: Build/Test also for 32-on-64 if available. * testsuite/systemtap.base/vta-test.stp: Take program under probe as @1. ----------------------------------------------------------------------- Summary of changes: testsuite/systemtap.base/vta-test.c | 45 ++++++++++++++++++++++++++------ testsuite/systemtap.base/vta-test.exp | 37 +++++++++++++++++++------- testsuite/systemtap.base/vta-test.stp | 2 +- 3 files changed, 64 insertions(+), 20 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-07-21 20:42 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=20100721204231.12682.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).