public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: cmeek@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.7-237-ga0e481c Date: Fri, 18 May 2012 19:01:00 -0000 [thread overview] Message-ID: <20120518190152.18636.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 a0e481c643e79b8ef33dfa6ae53c97dbf7a74f67 (commit) from 402ee2020d27b5e26a998b24f54b5b843a6fe5c2 (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 a0e481c643e79b8ef33dfa6ae53c97dbf7a74f67 Author: Chris Meek <cmeek@redhat.com> Date: Fri May 18 14:54:34 2012 -0400 PR13667: Fixed guru mode hook-not-defined bug Before, when in guru mode, it would pass the hook/priority strings across without checking/converting them to numbers. This caused a bug where perfectly legal strings (such as NF_IP_PRE_ROUTING) would be unrecognized in the generated code since their definitions are not available in kernel space. Now, it checks/converts all the strings to numbers whether in guru mode or not, but only complains about mismatches if not in guru mode. If in guru mode, it will still pass the initial string across if it doesn't match anything else. ----------------------------------------------------------------------- Summary of changes: tapset-netfilter.cxx | 169 ++++++++++++++++++++++++++------------------------ 1 files changed, 87 insertions(+), 82 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2012-05-18 19:01 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=20120518190152.18636.qmail@sourceware.org \ --to=cmeek@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: linkBe 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).