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.2-473-g86e56b9
Date: Mon, 12 Jul 2010 21:54:00 -0000	[thread overview]
Message-ID: <20100712215407.31513.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  86e56b940fbdfd38fe12529e1a8428e31d2245c0 (commit)
      from  a6da51a36fa8e653b8c6516a5f3286aae949ba05 (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 86e56b940fbdfd38fe12529e1a8428e31d2245c0
Author: Josh Stone <jistone@redhat.com>
Date:   Mon Jul 12 14:51:10 2010 -0700

    Better catch server errors in the testsuite
    
    If "avahi-browse ... | grep ..." doesn't find anything, like when a
    firewall blocks the way, we should catch that gracefully.  Use tcl's
    "catch" instead of "set" for this.
    
    * testsuite/lib/systemtap.exp (setup_server): Catch avahi-browse|grep
      when it falls.

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

Summary of changes:
 testsuite/lib/systemtap.exp |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)


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


                 reply	other threads:[~2010-07-12 21:54 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=20100712215407.31513.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).