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.3-256-gaf6a67d Date: Mon, 01 Nov 2010 20:37:00 -0000 [thread overview] Message-ID: <20101101203749.8774.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 af6a67d0f801ad6dbcbd01d4712cba77f1098adf (commit) from a8021985a74fe86cec06d257e5cf2ee5b43d1ba7 (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 af6a67d0f801ad6dbcbd01d4712cba77f1098adf Author: David Smith <dsmith@redhat.com> Date: Mon Nov 1 15:37:23 2010 -0500 Improved fork/vfork tests for RHEL5. * testsuite/systemtap.clone/dtrace_fork_exec.exp: Improve output string to handle parent/child execution order differences. * testsuite/systemtap.clone/dtrace_vfork_parent.c: Added include files to avoid compile error on RHEL5. * testsuite/systemtap.clone/dtrace_vfork_parent.c: Ditto. ----------------------------------------------------------------------- Summary of changes: testsuite/systemtap.clone/dtrace_fork_exec.exp | 4 +++- testsuite/systemtap.clone/dtrace_fork_parent.c | 2 ++ testsuite/systemtap.clone/dtrace_vfork_parent.c | 2 ++ 3 files changed, 7 insertions(+), 1 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-11-01 20:37 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=20101101203749.8774.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).