public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: jistone@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.2-25-g7ddf5da
Date: Wed, 31 Mar 2010 22:55:00 -0000	[thread overview]
Message-ID: <20100331225508.13697.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  7ddf5daac0d632ec2a1868d8c0e69bee086f25ee (commit)
       via  8a5f80d8b69c9d3497887c21dba64b5604651d17 (commit)
      from  4df79aaf86a9b6dfbccc3c51946024a30ba43726 (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 7ddf5daac0d632ec2a1868d8c0e69bee086f25ee
Author: Josh Stone <jistone@redhat.com>
Date:   Wed Mar 31 15:53:25 2010 -0700

    Make sure that the testsuite can find its server
    
    * testsuite/lib/systemtap.exp (setup_server): Use stap-find-servers to
      check that the firewall is letting us through to the server.

commit 8a5f80d8b69c9d3497887c21dba64b5604651d17
Author: Josh Stone <jistone@redhat.com>
Date:   Wed Mar 31 15:29:08 2010 -0700

    Use a different PATH approach for pfiles
    
        //bin/true && exec stap -g $0 ${1+"$@"}
    
    This keeps it as an entirely valid stap script, so manual stap
    invocation still works (as in pfiles.meta).

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

Summary of changes:
 testsuite/lib/systemtap.exp                     |    7 +++++++
 testsuite/systemtap.examples/process/pfiles.stp |    7 ++-----
 2 files changed, 9 insertions(+), 5 deletions(-)


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


                 reply	other threads:[~2010-03-31 22:55 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=20100331225508.13697.qmail@sourceware.org \
    --to=jistone@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).