public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: jistone@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-0.9.9-291-g6b66b9f
Date: Sat, 12 Sep 2009 00:37:00 -0000	[thread overview]
Message-ID: <20090912003723.6455.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  6b66b9f7f81a45d8ecce987dc4436efc1b94fad4 (commit)
      from  4f46087f18da349f124d7fd28721cd274b7176d1 (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 6b66b9f7f81a45d8ecce987dc4436efc1b94fad4
Author: Josh Stone <jistone@redhat.com>
Date:   Fri Sep 11 14:58:50 2009 -0700

    Remove duplicate uprobe_derived_probe code
    
    Much of uprobe_derived_probe is a straight copy of dwarf_derived_probe,
    and some of the comments even acknowledge this.  I'm instead making this
    an inheritance, so the duplication can be chopped away.
    
    * tapsets.cxx (struct dwarf_derived_probe): Reorganize for inheritance.
      (dwarf_derived_probe::dwarf_derived_probe): Adapt to handle process.
      (struct uprobe_derived_probe): Inherit from dwarf_derived_probe and
      remove duplicate members and methods.
      (uprobe_derived_probe::emit_module_decls): Member name changes.

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

Summary of changes:
 tapsets.cxx |  266 +++++++++++------------------------------------------------
 1 files changed, 47 insertions(+), 219 deletions(-)


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


                 reply	other threads:[~2009-09-12  0:37 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=20090912003723.6455.qmail@sourceware.org \
    --to=jistone@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).