public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: fche@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.3-291-gd255942
Date: Fri, 12 Nov 2010 21:34:00 -0000	[thread overview]
Message-ID: <20101112213420.1202.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  d255942829c56f4100ad937b37b52b3a37013a7a (commit)
       via  729f03c16603ad9c00e4d7d7b01d26cf0a067d32 (commit)
      from  a6085d747e71c8398084aac7e8f94dae8960ea3d (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 d255942829c56f4100ad937b37b52b3a37013a7a
Author: Frank Ch. Eigler <fche@elastic.org>
Date:   Fri Nov 12 16:33:43 2010 -0500

    tapset: add buildok test for inode_name()

commit 729f03c16603ad9c00e4d7d7b01d26cf0a067d32
Author: Jeff Moyer <jmoyer@redhat.com>
Date:   Fri Nov 12 16:29:20 2010 -0500

    tapset: new inode_name tapset function

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

Summary of changes:
 tapset/dentry.stp                     |   17 ++++++++++++++++-
 testsuite/buildok/dentry-embedded.stp |    1 +
 2 files changed, 17 insertions(+), 1 deletions(-)


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


                 reply	other threads:[~2010-11-12 21:34 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=20101112213420.1202.qmail@sourceware.org \
    --to=fche@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).