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.7-294-g99e1fb7 Date: Thu, 07 Jun 2012 20:56:00 -0000 [thread overview] Message-ID: <20120607205650.8858.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 99e1fb7afcdb21743d7f4555426744af22501905 (commit) from 5fae6ccbceb7a6524a84eecde86a1c1f43c38714 (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 99e1fb7afcdb21743d7f4555426744af22501905 Author: Josh Stone <jistone@redhat.com> Date: Thu Jun 7 13:46:38 2012 -0700 testsuite: Fix pretty-bits/char to work with relative paths This is more fallout from the automake update (commit c66be968a4ea) which led to relative $srcdir. The pretty-bits and pretty-char tests are passing $srcdir headers to @cast kernel types. That gets compiled with Kbuild, with the working directory is changed to the kernel root, so we need to give full paths for those headers. This adds a new tcl proc "fullpath" which inserts [pwd]/ on relative paths, and updates those pretty tests to use it. ----------------------------------------------------------------------- Summary of changes: testsuite/lib/systemtap.exp | 15 ++++++++++----- testsuite/systemtap.printf/pretty-bits.exp | 2 +- testsuite/systemtap.printf/pretty-char.exp | 2 +- 3 files changed, 12 insertions(+), 7 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2012-06-07 20:56 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=20120607205650.8858.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).