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.6-686-g19da035 Date: Thu, 26 Jan 2012 18:13:00 -0000 [thread overview] Message-ID: <20120126181302.17124.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 19da035139b241b33e1d7af398719e5b4f95e324 (commit) from 81ff0826bab5409faa5608d1b501f8fbf90d61b5 (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 19da035139b241b33e1d7af398719e5b4f95e324 Author: Josh Stone <jistone@redhat.com> Date: Thu Jan 26 10:11:23 2012 -0800 Don't squash to pass 4 when using --remote Our native_build check is a little too zealous, squashing runs to pass 4 when the local kernel doesn't match the command-line arguments. When we're running on a remote host, the local kernel is irrelevant. This issue only cropped up if the user provided explicit -r/-a arguments to match the remote -- otherwise the implicit searching was doing the right thing with matching each kernel. * session.cxx (systemtap_session::check_options): Remote targets don't care a whit whether the local kernel matches the build. ----------------------------------------------------------------------- Summary of changes: session.cxx | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2012-01-26 18:13 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=20120126181302.17124.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).