public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: serhei@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.8-192-g8d804a9 Date: Wed, 15 Aug 2012 15:37:00 -0000 [thread overview] Message-ID: <20120815153701.12556.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 8d804a9fc4bd4fceffb1cd037969f71b9962330b (commit) via afb0a364d10566ea951671fdde277724631c4961 (commit) from 39e63baec1c22a96ea87fce594c9bb71370c4078 (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 8d804a9fc4bd4fceffb1cd037969f71b9962330b Author: Serguei Makarov <smakarov@redhat.com> Date: Wed Aug 15 11:35:00 2012 -0400 PR14313: clarifying message for alias_suffixes.stp example. commit afb0a364d10566ea951671fdde277724631c4961 Author: Serguei Makarov <smakarov@redhat.com> Date: Wed Aug 15 11:31:59 2012 -0400 PR14313: rewrite alias suffix example in langref.tex. The rewrite avoids possible confusion due to the fact that there is a syscall.read.return alias defined in the tapset (which changes how the suffix is resolved in the real code vs. in the example with only one custom syscall.read alias). ----------------------------------------------------------------------- Summary of changes: doc/langref.tex | 41 ++++++++++++++----- .../systemtap.examples/general/alias_suffixes.stp | 4 ++ 2 files changed, 34 insertions(+), 11 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2012-08-15 15: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=20120815153701.12556.qmail@sourceware.org \ --to=serhei@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).