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.2-315-g95232e6
Date: Tue, 22 Jun 2010 18:00:00 -0000	[thread overview]
Message-ID: <20100622180054.19650.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  95232e6ba60af7d778dc84aca38af685ef49c7b5 (commit)
      from  305a3c4476e91749dcdacaaedf0b8198c9385cbb (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 95232e6ba60af7d778dc84aca38af685ef49c7b5
Author: David Smith <dsmith@redhat.com>
Date:   Tue Jun 22 13:00:34 2010 -0500

    Minor buildok testsuite fixes.
    
    * testsuite/buildok/inet_sock-embedded.stp: Added daddr_to_string() test.
    * testsuite/buildok/ioscheduler-detailed.stp: Added comment about why
      we're testing the iocheduler.*.kp probe aliases.

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

Summary of changes:
 testsuite/buildok/inet_sock-embedded.stp   |    1 +
 testsuite/buildok/ioscheduler-detailed.stp |    6 ++++++
 2 files changed, 7 insertions(+), 0 deletions(-)


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


                 reply	other threads:[~2010-06-22 18:00 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=20100622180054.19650.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).