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-0.7-48-g32637fc
Date: Thu, 07 Aug 2008 15:20:00 -0000	[thread overview]
Message-ID: <20080807152046.12400.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  32637fcca7e457d258c08415b87e94bb2d102bc0 (commit)
      from  940b7aa56b9c2e371d8a00c6e179ab2e9b4268ba (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 32637fcca7e457d258c08415b87e94bb2d102bc0
Author: David Smith <dsmith@redhat.com>
Date:   Thu Aug 7 10:20:13 2008 -0500

    'stap_compile' test procedure now ignores warnings
    2008-08-07  David Smith  <dsmith@redhat.com>
    
    	* systemtap.base/utrace_p4.exp: Uses lib/stap_compile.exp instead
    	of its own stap_compile procedure.
    	* systemtap.base/cache.exp (stap_compile): Ignores warnings.
    	* lib/stap_compile.exp: Ignores warnings.

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

Summary of changes:
 testsuite/ChangeLog                    |    7 +++++
 testsuite/lib/stap_compile.exp         |    1 +
 testsuite/systemtap.base/cache.exp     |    1 +
 testsuite/systemtap.base/utrace_p4.exp |   41 --------------------------------
 4 files changed, 9 insertions(+), 41 deletions(-)


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


                 reply	other threads:[~2008-08-07 15:20 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=20080807152046.12400.qmail@sourceware.org \
    --to=dsmith@sourceware.org \
    --cc=systemtap-cvs@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).