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, dsmith/task_finder2, updated. release-1.6-392-g6d7287a Date: Tue, 01 Nov 2011 20:53:00 -0000 [thread overview] Message-ID: <20111101205351.16340.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, dsmith/task_finder2 has been updated via 6d7287ac9e73d65401c2679e2531e37e0bf19ada (commit) from e3788742f276733de100bcef11940457ed36ea4a (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 6d7287ac9e73d65401c2679e2531e37e0bf19ada Author: David Smith <dsmith@redhat.com> Date: Tue Nov 1 15:53:26 2011 -0500 Cleanup task_finder2 by removing some unused code (ported). * runtime/task_finder2.c (__stp_utrace_attach_match_filename): Remove 'register_p' parameter (and associated code), since it was always set. (__stp_utrace_attach_match_tsk): Remove 'register_p' parameter. (__stp_utrace_task_finder_report_clone): Remove register_p parameter from __stp_utrace_attach_match_tsk() call. (__stp_utrace_task_finder_report_exec): Ditto. ----------------------------------------------------------------------- Summary of changes: runtime/task_finder2.c | 85 ++++++++--------------------------------------- 1 files changed, 15 insertions(+), 70 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-11-01 20:53 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=20111101205351.16340.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).