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.6-648-g68e60a3 Date: Thu, 22 Dec 2011 02:11:00 -0000 [thread overview] Message-ID: <20111222021151.25810.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 68e60a385a783dd0159b0342f61069a2909d4fe8 (commit) from b6ce8a9beabf3c7085ac9628806f82fe6bb58b72 (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 68e60a385a783dd0159b0342f61069a2909d4fe8 Author: Frank Ch. Eigler <fche@redhat.com> Date: Wed Dec 21 21:06:24 2011 -0500 tapset: separate env_var() from context.stp If it's left in context.stp, it will drag in tokenize.stp, which in turns drags in an unoptimizable %{ #define STAP_NEED_CONTEXT_TOKENIZE 1 %} which in turns enlarges the context. * tapset/context-envvar.stp: New file. Steal env_var() from ... * tapset/context.stp: ... from here. ----------------------------------------------------------------------- Summary of changes: doc/SystemTap_Tapset_Reference/tapsets.tmpl | 1 + tapset/context-envvar.stp | 57 +++++++++++++++++++++++++++ tapset/context.stp | 45 --------------------- 3 files changed, 58 insertions(+), 45 deletions(-) create mode 100644 tapset/context-envvar.stp hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-12-22 2:11 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=20111222021151.25810.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).