public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: brolley@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.0-209-gb513cd7 Date: Tue, 10 Nov 2009 19:28:00 -0000 [thread overview] Message-ID: <20091110192857.14694.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 b513cd75dac185ac258dc8260a01891c30be6251 (commit) via fd212bd5d99abc3518cf523eb7af2fea5ae206ba (commit) from f94baaeed17aba11aa46e9b46f0564217fc9978c (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 b513cd75dac185ac258dc8260a01891c30be6251 Merge: fd212bd5d99abc3518cf523eb7af2fea5ae206ba f94baaeed17aba11aa46e9b46f0564217fc9978c Author: Dave Brolley <brolley@redhat.com> Date: Tue Nov 10 14:26:34 2009 -0500 Merge branch 'master' of ssh://sources.redhat.com/git/systemtap commit fd212bd5d99abc3518cf523eb7af2fea5ae206ba Author: Dave Brolley <brolley@redhat.com> Date: Tue Nov 10 14:25:03 2009 -0500 Use 'module_realpath' instead of overwriting 'path' in insert_module. Update comments to clearly explain the security issues involved. ----------------------------------------------------------------------- Summary of changes: runtime/staprun/staprun_funcs.c | 32 ++++++++++++++------------------ 1 files changed, 14 insertions(+), 18 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2009-11-10 19: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: 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=20091110192857.14694.qmail@sourceware.org \ --to=brolley@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).