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.6-556-gbfffa44
Date: Thu, 08 Dec 2011 20:55:00 -0000	[thread overview]
Message-ID: <20111208205510.9255.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  bfffa44391cb6a701f6b7ce2b2f9d134ce2a585e (commit)
      from  78f63c471ba14bdde9036a5b8bdb9c1298af8d20 (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 bfffa44391cb6a701f6b7ce2b2f9d134ce2a585e
Author: Frank Ch. Eigler <fche@redhat.com>
Date:   Thu Dec 8 15:51:21 2011 -0500

    tracepoints: tolerate kernel event headers without their own #include <linux/tracepoint.h>
    
    include/trace/events/writeback.h lacks this, which means that
    systemtap tracepoint _aux.o files fail to build.
    
    * tapsets.cxx (tracepoint_derived_probe_group::emit_module_decls): Generously
      offer to emit the possibly missing #include <...> into the FOO_aux_N.c file.

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

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


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


                 reply	other threads:[~2011-12-08 20:55 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=20111208205510.9255.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).