public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: dsmith@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.7-312-gb19be2e
Date: Tue, 12 Jun 2012 21:49:00 -0000	[thread overview]
Message-ID: <20120612214911.25929.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  b19be2e289facccfc7874042ab431a6f58bb5a04 (commit)
      from  369bc6e2b40c4dcc595730d9127d7fdd4ab9de67 (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 b19be2e289facccfc7874042ab431a6f58bb5a04
Author: David Smith <dsmith@redhat.com>
Date:   Tue Jun 12 16:48:56 2012 -0500

    Add perf probe memory access tests.
    
    * testsuite/systemtap.stress/conversions.exp (run_conv_test): Add perf
      probe memory access test.
    * testsuite/systemtap.stress/conversions_perf.stp: New file.

-----------------------------------------------------------------------

Summary of changes:
 testsuite/systemtap.stress/conversions.exp         |    8 +++
 ...onversions_profile.stp => conversions_perf.stp} |   54 ++++++++++----------
 2 files changed, 35 insertions(+), 27 deletions(-)
 copy testsuite/systemtap.stress/{conversions_profile.stp => conversions_perf.stp} (76%)


hooks/post-receive
--
systemtap: system-wide probe/trace tool


                 reply	other threads:[~2012-06-12 21:49 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=20120612214911.25929.qmail@sourceware.org \
    --to=dsmith@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: link
Be 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).