public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: fche@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.3-248-gf58e7aa Date: Thu, 28 Oct 2010 22:45:00 -0000 [thread overview] Message-ID: <20101028224533.1402.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 f58e7aa8b145b05d7965b6dc31c2835d9da412f3 (commit) from 6be51dac7d0ac0fddf804b111c6f57b3775f6f11 (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 f58e7aa8b145b05d7965b6dc31c2835d9da412f3 Author: Frank Ch. Eigler <fche@elastic.org> Date: Thu Oct 28 18:42:35 2010 -0400 PR12169: fix tokenize() * tapset/tokenize.stp: New file for tokenize(). Use per-context statics. * doc/SystemTap_Tapset_Reference/tapsets.tmpl: Pull it into new docs. * tapset/string.stp: Remove old tokenize() code. * translate.cxx (emit_common_header): Add STAP_NEED_CONTEXT_TOKENIZE bits. (translate_pass): Emit global %{ %} embeds before context definition. ----------------------------------------------------------------------- Summary of changes: doc/SystemTap_Tapset_Reference/tapsets.tmpl | 1 + tapset/string.stp | 38 --------------------- tapset/tokenize.stp | 48 +++++++++++++++++++++++++++ translate.cxx | 14 +++++-- 4 files changed, 59 insertions(+), 42 deletions(-) create mode 100644 tapset/tokenize.stp hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-10-28 22:45 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=20101028224533.1402.qmail@sourceware.org \ --to=fche@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).