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.6-427-g5261f7a
Date: Fri, 18 Nov 2011 19:29:00 -0000	[thread overview]
Message-ID: <20111118192929.18665.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  5261f7ab82a4c5130e86d5ae3e3652515e7c92bc (commit)
      from  2db5adc1ea090630c2b87e1e8ce7b779f6e98639 (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 5261f7ab82a4c5130e86d5ae3e3652515e7c92bc
Author: David Smith <dsmith@redhat.com>
Date:   Fri Nov 18 13:28:54 2011 -0600

    Move common CONFIG_UTRACE check to its own function.
    
    * tapsets.cxx (check_process_probe_kernel_support): New function.
      (dwarf_builder::build): Moved CONFIG_UTRACE check to
      check_process_probe_kernel_support() which we call instead.
    * tapset-utrace.cxx (utrace_derived_probe::utrace_derived_probe): Call
      check_process_probe_kernel_support() instead of doing CONFIG_UTRACE
      check.
    * tapsets.h: Declare check_process_probe_kernel_support().

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

Summary of changes:
 tapset-utrace.cxx |    3 +--
 tapsets.cxx       |   14 ++++++++++++--
 tapsets.h         |    2 ++
 3 files changed, 15 insertions(+), 4 deletions(-)


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


                 reply	other threads:[~2011-11-18 19:29 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=20111118192929.18665.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).