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-264-ge8474d2 Date: Fri, 25 May 2012 16:05:00 -0000 [thread overview] Message-ID: <20120525160552.31142.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 e8474d2aac689025e8e540fa27ec68088bc5e468 (commit) from c49ffe6cbf1dce5ecf177f4b8aef28db7d77080b (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 e8474d2aac689025e8e540fa27ec68088bc5e468 Author: Frank Ch. Eigler <fche@redhat.com> Date: Fri May 25 12:04:04 2012 -0400 PR14168: sanitize $PATH for kbuild invocation * buildrun.cxx (make_any_make_cmd): Use env(1) to unset and change some environment variables, particularly $PATH. (run_make_cmd): Don't unsetenv here for the stap process any more. * testsuite/systemtap.base/kbuildenv.exp: Test it. * NEWS: Mention it. ----------------------------------------------------------------------- Summary of changes: NEWS | 4 ++++ buildrun.cxx | 28 +++++++++++++++------------- testsuite/systemtap.base/kbuildenv.exp | 14 ++++++++++++++ 3 files changed, 33 insertions(+), 13 deletions(-) create mode 100644 testsuite/systemtap.base/kbuildenv.exp hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2012-05-25 16:05 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=20120525160552.31142.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).