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.2-427-gbfdaad1
Date: Wed, 07 Jul 2010 15:10:00 -0000	[thread overview]
Message-ID: <20100707151023.19413.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  bfdaad1ea04409eb6568e7a440786e592b6756bb (commit)
      from  b80995d36d1e6b56ddb3c78a61d9dd41a2908421 (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 bfdaad1ea04409eb6568e7a440786e592b6756bb
Author: David Smith <dsmith@redhat.com>
Date:   Wed Jul 7 10:08:41 2010 -0500

    Fixed PR11663 by using an embedded-C expression to get the marker name/format.
    
    * tapset-mark.cxx (mark_var_expanding_visitor::visit_target_symbol_context):
      Instead of calling a tapset function to get the marker name/format, use
      an embedded-C expression.
    * tapsets.cxx (tracepoint_var_expanding_visitor::visit_target_symbol_context):
      Ditto.
    * tapset/marker.stp: Removed, since no longer needed.

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

Summary of changes:
 tapset-mark.cxx   |   25 ++++++++++++-------------
 tapset/marker.stp |   22 ----------------------
 tapsets.cxx       |   11 ++++++-----
 3 files changed, 18 insertions(+), 40 deletions(-)
 delete mode 100644 tapset/marker.stp


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


                 reply	other threads:[~2010-07-07 15:10 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=20100707151023.19413.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).