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-0.9.5-151-gbe8770c Date: Fri, 17 Apr 2009 14:37:00 -0000 [thread overview] Message-ID: <20090417143727.5598.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 be8770ce0c66eea1113c3c91682b4fdf6ae1ec77 (commit) from 889c4638f741163395438aca60226ff8a5e2009e (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 be8770ce0c66eea1113c3c91682b4fdf6ae1ec77 Author: David Smith <dsmith@redhat.com> Date: Fri Apr 17 09:37:00 2009 -0500 Added new utrace syscall argument test. 2009-04-17 David Smith <dsmith@redhat.com> * systemtap.base/utrace_syscall_args.c: New test file. * systemtap.base/utrace_syscall_args.exp: New test file. * systemtap.base/utrace_syscall_args.stp: New test file. ----------------------------------------------------------------------- Summary of changes: testsuite/systemtap.base/utrace_syscall_args.c | 67 ++++ testsuite/systemtap.base/utrace_syscall_args.exp | 82 +++++ testsuite/systemtap.base/utrace_syscall_args.stp | 366 ++++++++++++++++++++++ 3 files changed, 515 insertions(+), 0 deletions(-) create mode 100644 testsuite/systemtap.base/utrace_syscall_args.c create mode 100644 testsuite/systemtap.base/utrace_syscall_args.exp create mode 100644 testsuite/systemtap.base/utrace_syscall_args.stp hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2009-04-17 14: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=20090417143727.5598.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).