public inbox for
help / color / mirror / Atom feed
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.7-251-g0a892a4
Date: Wed, 23 May 2012 15:30:00 -0000	[thread overview]
Message-ID: <> (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  0a892a4409cb4cc241a8d6c77bef9e31c545c186 (commit)
       via  da00b50e8da8b19893e9bbcce39ed22eeed745ba (commit)
      from  57db0e6f972d6fb405e4b9243404a3b15052bbb4 (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 0a892a4409cb4cc241a8d6c77bef9e31c545c186
Author: Serguei Makarov <>
Date:   Wed May 23 11:26:52 2012 -0400

    Initial (barely adequate) reference doc for netfilter.stp.

commit da00b50e8da8b19893e9bbcce39ed22eeed745ba
Author: Serguei Makarov <>
Date:   Wed May 23 11:22:26 2012 -0400

    Added section describing netfilter probes to stapprobes.3stap.
    Note that the link to tapset::netfilter (3stap) is currently broken.
    That man page is waiting on a fix for PR14146. If that bug gets delayed
    indefinitely, it may be necessary to delete the reference for the time
    being, and refer people to the Tapset Reference document instead.


Summary of changes:
 doc/SystemTap_Tapset_Reference/tapsets.tmpl |    1 +
 stapprobes.3stap                            |  112 +++++++++++++++++++++++++++
 tapset/netfilter.stp                        |   13 ++--
 3 files changed, 119 insertions(+), 7 deletions(-)

systemtap: system-wide probe/trace tool

                 reply	other threads:[~2012-05-23 15:30 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).