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.1-68-g1f6cb79
Date: Mon, 08 Feb 2010 21:59:00 -0000	[thread overview]
Message-ID: <20100208215958.28870.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  1f6cb79459e181448d6e4e37381b57325b6d0fdb (commit)
      from  189559623dcda793b1ae9ade54299f5c7a775b76 (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 1f6cb79459e181448d6e4e37381b57325b6d0fdb
Author: David Smith <dsmith@redhat.com>
Date:   Mon Feb 8 15:59:29 2010 -0600

    Fixed BZ559643 by doing 'spawn;expect;wait' instead of 'spawn;wait;expect'.
    
    * testsuite/systemtap.base/labels.exp: Corrected order of
      'spawn;expect;wait' calls.  Added 'wait' calls when needed.  Also,
      doesn't run the "labels exe .label" test if uprobes isn't supported.

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

Summary of changes:
 testsuite/systemtap.base/labels.exp |   43 +++++++++++++++++++++-------------
 1 files changed, 26 insertions(+), 17 deletions(-)


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


                 reply	other threads:[~2010-02-08 21:59 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=20100208215958.28870.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).