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-1.5-31-g0bbb800
Date: Tue, 07 Jun 2011 18:25:00 -0000	[thread overview]
Message-ID: <20110607182515.18037.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  0bbb80098decc9c4c43a1800538007d86b600bba (commit)
      from  26f7a1812269f1cbeb06d93016856303c8bd12a3 (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 0bbb80098decc9c4c43a1800538007d86b600bba
Author: Josh Stone <jistone@redhat.com>
Date:   Tue Jun 7 11:23:13 2011 -0700

    stapconf: Conditionalize stacktrace_ops.warning{,_symbol}
    
    Kernel commit 449a66f removed these fields.
    
    * buildrun.cxx: Include the new test.
    * runtime/autoconf-stacktrace_ops-warning.c: Check the warning field.
    * runtime/stack.c: Conditionalize the warning initialization.

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

Summary of changes:
 buildrun.cxx                                       |    2 ++
 ...k-stack.c => autoconf-stacktrace_ops-warning.c} |    4 ++--
 runtime/stack.c                                    |    4 ++++
 3 files changed, 8 insertions(+), 2 deletions(-)
 copy runtime/{autoconf-walk-stack.c => autoconf-stacktrace_ops-warning.c} (52%)


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


                 reply	other threads:[~2011-06-07 18:25 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=20110607182515.18037.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).