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.6-598-g2cf2514
Date: Thu, 15 Dec 2011 15:49:00 -0000	[thread overview]
Message-ID: <20111215154929.6765.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  2cf251473fcdde2cdc2d74a5ef6240478383337c (commit)
      from  7bec2ae95b347fac54d2c54a9f1884a43ff8d68a (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 2cf251473fcdde2cdc2d74a5ef6240478383337c
Author: David Smith <dsmith@redhat.com>
Date:   Thu Dec 15 09:49:13 2011 -0600

    Fix PR12413 by fixing 'kprocess.release' variable problems.
    
    * tapset/kprocess.stp: Deprecate 'pid' variable and fix 'released_pid' and
      'released_tid' variables in the kprocess.release probe.
    * testsuite/buildok/kprocess-detailed.stp: Update kprocess.release test.
    * NEWS: Mention kprocess.release 'pid' variable deprecation.
    * stap.1: Ditto.

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

Summary of changes:
 NEWS                                    |    4 ++++
 stap.1                                  |    5 +++++
 tapset/kprocess.stp                     |    8 +++++---
 testsuite/buildok/kprocess-detailed.stp |    5 ++++-
 4 files changed, 18 insertions(+), 4 deletions(-)


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


                 reply	other threads:[~2011-12-15 15: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=20111215154929.6765.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).