public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: mark@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.6-513-g031b950
Date: Tue, 29 Nov 2011 16:56:00 -0000	[thread overview]
Message-ID: <20111129165602.8885.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  031b950f73a6317b31bf2c8f64b3658605e69485 (commit)
      from  3cd429bb5f0ed17957442f690728e127430d2527 (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 031b950f73a6317b31bf2c8f64b3658605e69485
Author: Mark Wielaard <mjw@redhat.com>
Date:   Tue Nov 29 17:53:35 2011 +0100

    Make cast-scope testcase more robust. Prevent line-reordening.
    
    Setting a statement line probe is somewhat fragile since different GCCs
    output different line tables. Make sure that there is a known single
    statement line in the testcase to probe.

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

Summary of changes:
 testsuite/systemtap.base/cast-scope.cxx |    7 ++++++-
 testsuite/systemtap.base/cast-scope.stp |    2 +-
 2 files changed, 7 insertions(+), 2 deletions(-)


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


                 reply	other threads:[~2011-11-29 16:56 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=20111129165602.8885.qmail@sourceware.org \
    --to=mark@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).