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.2-20-geda8b44
Date: Tue, 30 Mar 2010 16:53:00 -0000	[thread overview]
Message-ID: <20100330165259.32520.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  eda8b449152cf0f864d2cd250fb2b7a2945bc996 (commit)
       via  d8fd2e985cd815704a50d6ef9657f1aa319de1a4 (commit)
      from  8a1d8fbf543260108adf064fe368399dc477567e (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 eda8b449152cf0f864d2cd250fb2b7a2945bc996
Author: Frank Ch. Eigler <fche@elastic.org>
Date:   Tue Mar 30 12:50:55 2010 -0400

    testsuite: convert pfiles.stp to $PATH-based stap invocation form

commit d8fd2e985cd815704a50d6ef9657f1aa319de1a4
Author: Frank Ch. Eigler <fche@elastic.org>
Date:   Tue Mar 30 09:59:10 2010 -0400

    testsuite: use #! /usr/bin/env stap instead of /usr/bin/stap

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

Summary of changes:
 testsuite/systemtap.examples/process/pfiles.stp    |    8 +++++++-
 testsuite/systemtap.examples/profiling/fntimes.stp |    2 +-
 .../systemtap.examples/profiling/thread-times.stp  |    2 +-
 3 files changed, 9 insertions(+), 3 deletions(-)


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


                 reply	other threads:[~2010-03-30 16:53 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=20100330165259.32520.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: 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).