public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: mark@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.6-44-g0d89793
Date: Mon, 01 Aug 2011 14:17:00 -0000	[thread overview]
Message-ID: <20110801141743.6882.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  0d8979326b672bfb7570ea76d598a7c23f3b81f5 (commit)
      from  49e1b0a11e3337ef37152eefc0f119c76cb91ff3 (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 0d8979326b672bfb7570ea76d598a7c23f3b81f5
Author: Mark Wielaard <mjw@redhat.com>
Date:   Mon Aug 1 16:00:05 2011 +0200

    Probe context data field is only used for procfs. Rename to procfs_data.
    
    itrace and mark probes would also scribble (useless) data into this
    context field, without ever using it, for no apparent reason, except
    that they had "data" around. Renamed the field to procfs_data to make
    clear it has a specific purpose.
    
    Also add documentation for remaining undocumented common_probe_context fields.

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

Summary of changes:
 runtime/common_probe_context.h |   25 +++++++++++++++++++++++--
 tapset-itrace.cxx              |    1 -
 tapset-mark.cxx                |    1 -
 tapset-procfs.cxx              |   14 +++++++-------
 4 files changed, 30 insertions(+), 11 deletions(-)


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


                 reply	other threads:[~2011-08-01 14:17 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=20110801141743.6882.qmail@sourceware.org \
    --to=mark@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).