public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: scox@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, roland/new-sdt, updated. release-1.3-60-g1baa81f
Date: Thu, 09 Sep 2010 20:50:00 -0000	[thread overview]
Message-ID: <20100909205016.25179.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, roland/new-sdt has been updated
       via  1baa81fdaf52a55ec0593a7d7e98f1243644080a (commit)
      from  9c70e3781e25ccfb03c8a39f31a0f767717d8b88 (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 1baa81fdaf52a55ec0593a7d7e98f1243644080a
Author: Stan Cox <scox@redhat.com>
Date:   Thu Sep 9 16:42:00 2010 -0400

    Fix sdt.h int argument access.
    
    * tapsets.cxx (sdt_uprobe_var_expanding_visitor::visit_target_symbol):
    Always access sdt.h int arguments with user_int.
    
    * postgres.exp (run_tests):  Add verbose stap command message.

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

Summary of changes:
 tapsets.cxx                           |    4 ++--
 testsuite/systemtap.apps/postgres.exp |    2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)


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


                 reply	other threads:[~2010-09-09 20:50 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=20100909205016.25179.qmail@sourceware.org \
    --to=scox@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).