public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: jistone@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.4-36-g4b12854 Date: Fri, 28 Jan 2011 23:08:00 -0000 [thread overview] Message-ID: <20110128230835.28040.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 4b128546ae4c65b56615aba180a52cefc509a217 (commit) from 2e3739d2d8b728145afcbbf9c527e7d383f43922 (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 4b128546ae4c65b56615aba180a52cefc509a217 Author: Josh Stone <jistone@redhat.com> Date: Fri Jan 28 15:02:50 2011 -0800 Assert that TMPDIR, if set, is a boring path We don't want any excitement in the paths we must use. e.g. Kbuild doesn't cope well with spaces in the M="/module path" * session.cxx (systemtap_session::check_options): Restrict the characters allowed in TMPDIR to a universally-safe set. * testsuite/parseko/cmdline22.stp: New, check that TMPDIR spaces are not allowed, even if that path really exists. ----------------------------------------------------------------------- Summary of changes: session.cxx | 6 ++++++ testsuite/parseko/cmdline22.stp | 16 ++++++++++++++++ 2 files changed, 22 insertions(+), 0 deletions(-) create mode 100755 testsuite/parseko/cmdline22.stp hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-01-28 23:08 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=20110128230835.28040.qmail@sourceware.org \ --to=jistone@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).