public inbox for
help / color / mirror / Atom feed
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.7-314-g0386bbc
Date: Wed, 13 Jun 2012 14:40:00 -0000	[thread overview]
Message-ID: <> (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  0386bbcfaf726f9bc1eec798e62229e8e298549c (commit)
       via  25b24f3675cc75b3740955f9f1098b5c12733a4b (commit)
      from  b19be2e289facccfc7874042ab431a6f58bb5a04 (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 0386bbcfaf726f9bc1eec798e62229e8e298549c
Author: Serguei Makarov <>
Date:   Wed Jun 13 10:40:03 2012 -0400

    PR10299: enable support for arbitrary mangling (first without breaking existing behaviour).

commit 25b24f3675cc75b3740955f9f1098b5c12733a4b
Author: Serguei Makarov <>
Date:   Wed Jun 13 10:33:17 2012 -0400

    PR10299 groundwork: tests to check old and new behaviour.


Summary of changes:
 dwflpp.cxx                        |   26 +++---
 tapset-netfilter.cxx              |   12 +-
 tapset-procfs.cxx                 |    8 +-
 tapsets.cxx                       |    2 +-
 testsuite/buildok/newlocals01.stp |   14 +++
 testsuite/buildok/oldlocals01.stp |   16 +++
 translate.cxx                     |  210 +++++++++++++++++++++++++------------
 translate.h                       |    9 ++-
 8 files changed, 207 insertions(+), 90 deletions(-)
 create mode 100755 testsuite/buildok/newlocals01.stp
 create mode 100755 testsuite/buildok/oldlocals01.stp

systemtap: system-wide probe/trace tool

                 reply	other threads:[~2012-06-13 14:40 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).