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, master, updated. release-0.9.7-199-gad00230
Date: Tue, 09 Jun 2009 02:00:00 -0000	[thread overview]
Message-ID: <20090609020020.25519.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  ad002306b50c6cc3c3601fac31dfe3ecf23749fb (commit)
      from  f517ee24c58413f7de89ede71c728579c12ace5b (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 ad002306b50c6cc3c3601fac31dfe3ecf23749fb
Author: Stan Cox <scox@redhat.com>
Date:   Mon Jun 8 21:57:44 2009 -0400

    * tapsets.cxx (probe_table): Make mark_name and sess refs.
    (probe_table::get_next_probe): Dissect using struct probe_table.
    (sdt_var_expanding_visitor): Use lex_cast.
    (dwarf_builder::build): Copy probe and location for TOK_MARK cases.
    Call derive_probes for kprobe and utrace cases.

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

Summary of changes:
 tapsets.cxx |  230 +++++++++++++++++++++++++++++-----------------------------
 1 files changed, 115 insertions(+), 115 deletions(-)


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


                 reply	other threads:[~2009-06-09  2:00 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=20090609020020.25519.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).