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-0.7-656-g406d830 Date: Wed, 07 Jan 2009 00:33:00 -0000 [thread overview] Message-ID: <20090107003324.2713.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 406d830652cc659fe420dcf5b54398ea22310750 (commit) via ec77429d7f3b6e5bc6bb8a93beb8dac6c6dd99b1 (commit) from 37978f16f382360bef160017d4e1803d0c56244b (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 406d830652cc659fe420dcf5b54398ea22310750 Author: Frank Ch. Eigler <fche@elastic.org> Date: Tue Jan 6 19:32:24 2009 -0500 PR9699: tapset changes for STAPCONF_TASK_UID for *uid()/*gid() calls commit ec77429d7f3b6e5bc6bb8a93beb8dac6c6dd99b1 Author: Frank Ch. Eigler <fche@elastic.org> Date: Tue Jan 6 19:30:17 2009 -0500 PR9699: tweak autoconf file for Strict C Language Standards Compliance (tm) ----------------------------------------------------------------------- Summary of changes: runtime/autoconf-task-uid.c | 5 +++-- tapset/ChangeLog | 5 +++++ tapset/context.stp | 18 +++++++++++++++++- tapset/task.stp | 35 +++++++++++++++++++++++++++++++++++ 4 files changed, 60 insertions(+), 3 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2009-01-07 0:33 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=20090107003324.2713.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).