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.0-91-g784a7d5
Date: Tue, 13 Oct 2009 18:59:00 -0000	[thread overview]
Message-ID: <20091013185933.11028.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  784a7d570306d7601a7338c95226a49dec156398 (commit)
       via  aafa7871f89484e36a7554cd943b4f827f4e3112 (commit)
      from  07940db192f25caf77b9ffbb7d35150ace5d5404 (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 784a7d570306d7601a7338c95226a49dec156398
Author: Josh Stone <jistone@redhat.com>
Date:   Tue Oct 13 11:59:23 2009 -0700

    Let semko/utrace.stp fail even with CONFIG_UTRACE=y

commit aafa7871f89484e36a7554cd943b4f827f4e3112
Author: Josh Stone <jistone@redhat.com>
Date:   Tue Oct 13 11:50:34 2009 -0700

    Add a test for CONFIG_FOO wildcards

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

Summary of changes:
 testsuite/semko/utrace.stp          |    2 +-
 testsuite/semok/config_wildcard.stp |   25 +++++++++++++++++++++++++
 2 files changed, 26 insertions(+), 1 deletions(-)
 create mode 100755 testsuite/semok/config_wildcard.stp


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


                 reply	other threads:[~2009-10-13 18: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=20091013185933.11028.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).