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-0.9.5-126-g1f65cc4 Date: Tue, 14 Apr 2009 20:26:00 -0000 [thread overview] Message-ID: <20090414202634.27242.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 1f65cc4ffd1bd362b10d7f07d1cb9c4e7de68027 (commit) via 891e4fb2d5bf81b540b66b126b2ba78d1b7f459b (commit) from b9c1e0228f6c629e278820caf40870cdad285441 (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 1f65cc4ffd1bd362b10d7f07d1cb9c4e7de68027 Author: Josh Stone <jistone@redhat.com> Date: Tue Apr 14 12:34:12 2009 -0700 PR9953: split up the two process.* tapsets The overlapping process.* tapsets are now separated. Those probe points documented in stapprobes(3stap) remain the same. Those that were formerly in stapprobes.process(3stap) have been renamed to kprocess, to reflect their kernel perspective on processes. commit 891e4fb2d5bf81b540b66b126b2ba78d1b7f459b Author: Josh Stone <jistone@redhat.com> Date: Tue Apr 14 11:49:15 2009 -0700 Adjust NEWS indentation ----------------------------------------------------------------------- Summary of changes: Makefile.am | 2 +- Makefile.in | 8 ++-- NEWS | 33 +++++++++++-------- configure | 4 +- configure.ac | 2 +- doc/SystemTap_Beginners_Guide/en-US/References.xml | 2 +- doc/SystemTap_Tapset_Reference/tapsets.tmpl | 6 ++-- .../en-US/Tapset_Dev_Guide.xml | 4 +- ...ocess.3stap.in => stapprobes.kprocess.3stap.in} | 22 ++++++------ tapset/DEVGUIDE | 6 ++-- tapset/{process.stp => kprocess.stp} | 30 +++++++++--------- testsuite/buildok/process-all-probes.stp | 12 +++--- testsuite/buildok/process_test.stp | 12 +++--- .../systemtap.examples/process/proc_snoop.stp | 12 +++--- testsuite/systemtap.stress/whitelist.exp | 1 + 15 files changed, 81 insertions(+), 75 deletions(-) rename man/{stapprobes.process.3stap.in => stapprobes.kprocess.3stap.in} (73%) rename tapset/{process.stp => kprocess.stp} (73%) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2009-04-14 20:26 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=20090414202634.27242.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).