public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: mark@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-0.9.5-97-g07cee54 Date: Wed, 08 Apr 2009 09:36:00 -0000 [thread overview] Message-ID: <20090408093612.19449.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 07cee54d6fb720d4300972aaff9300ac8028c88d (commit) via 48cde708db9e1662047def94c2dfd7ffe28aa765 (commit) from a7f1270e24a77ab8338604ab14ee928a421f89a0 (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 07cee54d6fb720d4300972aaff9300ac8028c88d Author: Mark Wielaard <mjw@redhat.com> Date: Wed Apr 8 11:11:34 2009 +0200 Use _stp_snprintf in _stp_symbol_snprint. * runtime/sym.c (_stp_symbol_snprint): Use _stp_snprintf, no _stp_printf. commit 48cde708db9e1662047def94c2dfd7ffe28aa765 Author: Mark Wielaard <mjw@redhat.com> Date: Wed Apr 8 10:59:27 2009 +0200 Add uaddr() context tapset function. * tapset/context.stp (uaddr): New sfunction. * testsuite/buildok/uaddr.stp: New test. ----------------------------------------------------------------------- Summary of changes: runtime/sym.c | 4 ++-- tapset/context.stp | 25 +++++++++++++++++++++++++ testsuite/buildok/uaddr.stp | 8 ++++++++ 3 files changed, 35 insertions(+), 2 deletions(-) create mode 100755 testsuite/buildok/uaddr.stp hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2009-04-08 9:36 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=20090408093612.19449.qmail@sourceware.org \ --to=mark@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).