public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: wcohen@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.3-6-gd8878d9
Date: Thu, 22 Jul 2010 20:49:00 -0000	[thread overview]
Message-ID: <20100722204930.2626.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  d8878d94c80eaee7dea0743b741d04961dfab4ef (commit)
       via  e9e9967b2a5f95e15328c30d6d7c2c7a204f6e4f (commit)
      from  5113a70b9eaa97a9230bbd849dca6f7886b107f4 (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 d8878d94c80eaee7dea0743b741d04961dfab4ef
Author: William Cohen <wcohen@redhat.com>
Date:   Thu Jul 22 16:47:58 2010 -0400

    Move inodewatch.stp into the examples
    
    Originally inodewatch.stp was in the beginner guide's extras directory.
    Moving inodewatch.stp into the examples directory to get regular testing
    of the script.

commit e9e9967b2a5f95e15328c30d6d7c2c7a204f6e4f
Author: William Cohen <wcohen@redhat.com>
Date:   Thu Jul 22 16:15:06 2010 -0400

    Clean up the inodewatch-simple.stp to just be inodewatch.stp
    
    This addresses the issues in Red Hat bz617057. Also simplify the script
    to make use of the tapset variables dev/ino and MKDEV functions.

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

Summary of changes:
 .../en-US/Useful_Scripts-inodewatch.xml            |    6 ++----
 .../en-US/extras/inodewatch-simple.stp             |    9 ---------
 testsuite/systemtap.examples/index.html            |    3 +++
 testsuite/systemtap.examples/index.txt             |    8 ++++++++
 testsuite/systemtap.examples/io/inodewatch.meta    |   13 +++++++++++++
 testsuite/systemtap.examples/io/inodewatch.stp     |   10 ++++++++++
 testsuite/systemtap.examples/keyword-index.html    |    3 +++
 testsuite/systemtap.examples/keyword-index.txt     |    8 ++++++++
 8 files changed, 47 insertions(+), 13 deletions(-)
 delete mode 100644 doc/SystemTap_Beginners_Guide/en-US/extras/inodewatch-simple.stp
 create mode 100755 testsuite/systemtap.examples/io/inodewatch.meta
 create mode 100755 testsuite/systemtap.examples/io/inodewatch.stp


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


                 reply	other threads:[~2010-07-22 20: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=20100722204930.2626.qmail@sourceware.org \
    --to=wcohen@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).