public inbox for
help / color / mirror / Atom feed
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.7-236-g402ee20
Date: Fri, 18 May 2012 14:28: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  402ee2020d27b5e26a998b24f54b5b843a6fe5c2 (commit)
       via  6f63671072dc7715569b67ed3672f917ecc47c2f (commit)
       via  cf9a931bafb23af46a7497bfa822d2520ec5b60c (commit)
      from  b48233fdf8017f32a94ca2f4f36e7c16d75e94e5 (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 402ee2020d27b5e26a998b24f54b5b843a6fe5c2
Author: Chris Meek <>
Date:   Fri May 18 10:23:31 2012 -0400

    PR13667: Tweak verdict-needs-guru error message

commit 6f63671072dc7715569b67ed3672f917ecc47c2f
Author: Chris Meek <>
Date:   Wed May 16 17:25:37 2012 -0400

    PR13667: Added guru mode requirement for $verdict
    guru mode is needed to write to $verdict, for obvious reasons

commit cf9a931bafb23af46a7497bfa822d2520ec5b60c
Author: Chris Meek <>
Date:   Wed May 16 16:52:35 2012 -0400

    PR13667: Range checking for hooks and priorities
    - Added more strict range checking for hook names
    - Added support for arp and bridge netfilter hooks
    - Added range checking of priority strings for ipv4
      and ipv6 hooks, numerical checking for all


Summary of changes:
 tapset-netfilter.cxx |  139 ++++++++++++++++++++++++++++++++++++++++++--------
 1 files changed, 118 insertions(+), 21 deletions(-)

systemtap: system-wide probe/trace tool

                 reply	other threads:[~2012-05-18 14:28 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).