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.0-246-gf210735
Date: Wed, 18 Nov 2009 17:00:00 -0000	[thread overview]
Message-ID: <20091118170012.2922.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  f2107354d0a07d8f1d3bb3e97920ba557ebe7855 (commit)
      from  f3c4da447c5b8746e2f756f2ed1dd16c7834bdb2 (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 f2107354d0a07d8f1d3bb3e97920ba557ebe7855
Author: David Smith <dsmith@redhat.com>
Date:   Wed Nov 18 10:59:37 2009 -0600

    PR 5150.  Fixed nfs tapset by making probes optional.
    * tapset/nfs_proc.stp: Made 'nfs.proc.read', 'nfs.proc.write', and
      'nfs.proc.commit' optional for newer kernels without those functions.
    * testsuite/systemtap.pass1-4/buildok.exp: Expect nfs-all-probes.stp to
      pass.

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

Summary of changes:
 tapset/nfs_proc.stp                     |   52 ++++++++++++++++++-------------
 testsuite/systemtap.pass1-4/buildok.exp |    1 -
 2 files changed, 30 insertions(+), 23 deletions(-)


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


                 reply	other threads:[~2009-11-18 17: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=20091118170012.2922.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).