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.2-174-gef42866 Date: Wed, 26 May 2010 01:19:00 -0000 [thread overview] Message-ID: <20100526011911.22787.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 ef42866719716b504ec0dce41ce61e5ed4ab7822 (commit) via 6f551a697a7724aa3f1be3319898531372c67319 (commit) from f83336a5d28bfe5c29bc31cd161abb4044fb4281 (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 ef42866719716b504ec0dce41ce61e5ed4ab7822 Author: Frank Ch. Eigler <fche@elastic.org> Date: Tue May 25 21:17:25 2010 -0400 PR10245: allow "-" in sdt.h marker names * tapsets.cxx (sdt_query ctor): Map - to __ in incoming marker names. * NEWS: Note it. * testsuite/systemtap.base/sdt_types.c, sdt_misc.exp: Test it. commit 6f551a697a7724aa3f1be3319898531372c67319 Author: Frank Ch. Eigler <fche@elastic.org> Date: Tue May 25 21:03:43 2010 -0400 make semok/thirtysix.stp test use stap -p2 instead of -p4 ----------------------------------------------------------------------- Summary of changes: NEWS | 4 ++++ tapsets.cxx | 12 +++++++++++- testsuite/semok/thirtysix.stp | 2 +- testsuite/systemtap.base/sdt_misc.exp | 12 ++++++++++-- testsuite/systemtap.base/sdt_types.c | 1 + 5 files changed, 27 insertions(+), 4 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-05-26 1:19 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=20100526011911.22787.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).