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.8-162-g2dd2f7e
Date: Tue, 07 Aug 2012 22:32:00 -0000	[thread overview]
Message-ID: <20120807223239.7662.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  2dd2f7ec7670a4dbf1f6a36d5e672300073b65b7 (commit)
      from  10c737ff1e6149ecf183a1839d722873e57dbb14 (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 2dd2f7ec7670a4dbf1f6a36d5e672300073b65b7
Author: David Smith <dsmith@redhat.com>
Date:   Tue Aug 7 17:32:01 2012 -0500

    Fix problems with varargs macros in dyninst/io.c.
    
    * runtime/dyninst/io.c: Convert _stp_warn(), _stp_error(),
      _stp_softerror(), and _stp_dbug() from varargs macros into varargs
      functions so that calling _stp_warn() (for example) with just a format
      argument works correctly.

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

Summary of changes:
 runtime/dyninst/io.c |   75 ++++++++++++++++++++++++++++++++++++++++++++++---
 1 files changed, 70 insertions(+), 5 deletions(-)


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


                 reply	other threads:[~2012-08-07 22:32 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=20120807223239.7662.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).