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.7-252-gddbda7e Date: Wed, 23 May 2012 16:39:00 -0000 [thread overview] Message-ID: <20120523163947.786.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 ddbda7ee737b903544eb027f5b0a304b39dbb86e (commit) from 0a892a4409cb4cc241a8d6c77bef9e31c545c186 (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 ddbda7ee737b903544eb027f5b0a304b39dbb86e Author: Frank Ch. Eigler <fche@redhat.com> Date: Wed May 23 12:37:54 2012 -0400 PR14137: tolerate duplicate netfilter hook probe handlers translate.cxx may model duplicate probe handlers by changing multiple *_derived_probe ->name's to the same string, which upsets tapset-netfilter.cxx code generation. Use an index for the contexts where required. * tapset-netfilter.cxx (netfilter_derived_probe ctor): Assign unique nf_filter index. (emit_module_decls, emit_module_init, emit_module_exit): Use when appropriate. ----------------------------------------------------------------------- Summary of changes: tapset-netfilter.cxx | 21 ++++++++++++++------- 1 files changed, 14 insertions(+), 7 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2012-05-23 16:39 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=20120523163947.786.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: 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).