public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: fche@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.3-244-g75ae2ec
Date: Thu, 28 Oct 2010 17:34:00 -0000	[thread overview]
Message-ID: <20101028173416.5634.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  75ae2ec9242922d9c3818a720d456aca7901d771 (commit)
      from  4ed03d392476139c36d1959400909c80f533f651 (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 75ae2ec9242922d9c3818a720d456aca7901d771
Author: Frank Ch. Eigler <fche@elastic.org>
Date:   Thu Oct 28 13:31:26 2010 -0400

    tracepoints: restore access to include/trace/event/* points w/o debuginfo
    
    An earlier commit impeded access to kernel tracepoints that are
    defined in the proper header files, but lacking the debuginfo
    for the backup searching widget to work.
    
    * tapsets.cxx (tracepoint_derived_probe_group::emit_module_decls):
      Remove "include/" substring from header files.

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

Summary of changes:
 tapsets.cxx |   11 ++++++++---
 1 files changed, 8 insertions(+), 3 deletions(-)


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


                 reply	other threads:[~2010-10-28 17:34 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=20101028173416.5634.qmail@sourceware.org \
    --to=fche@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).