public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: dsmith@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.7-23-g8a33235 Date: Fri, 10 Feb 2012 21:46:00 -0000 [thread overview] Message-ID: <20120210214641.2304.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 8a332350d63c3fb72c2e062724400ce814246425 (commit) from 021bc902453a4b7375ca5b575c1bf1c980d43f81 (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 8a332350d63c3fb72c2e062724400ce814246425 Author: David Smith <dsmith@redhat.com> Date: Fri Feb 10 15:45:20 2012 -0600 (Fixed PR13681) Bulk mode scripts no longer leave the module behind on rhel4. * runtime/staprun/relay_old.c (close_relayfs_files): 0 can be a valid relay_fd[cpu] value. (open_relayfs_files): On error, initialize relay_fd[cpu] to -1, not 0. (init_oldrelayfs): Initialize relay_fd[cpu] to -1, not 0. ----------------------------------------------------------------------- Summary of changes: runtime/staprun/relay_old.c | 12 ++++++------ 1 files changed, 6 insertions(+), 6 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2012-02-10 21:46 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=20120210214641.2304.qmail@sourceware.org \ --to=dsmith@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).