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-290-g50b7269 Date: Mon, 10 Oct 2011 10:22:00 -0000 [thread overview] Message-ID: <20111010102238.8380.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 50b726929d10d1cbe8c7a1c396d0ee63096d80da (commit) via 0b9c887e33c06cb62bc21b99f7d9e18b6ca7f603 (commit) from c9ccb642c453d05af5afdc2c9769e475ba3255e8 (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 50b726929d10d1cbe8c7a1c396d0ee63096d80da Author: Han Pingtian <phan@redhat.com> Date: Mon Oct 10 06:12:37 2011 -0400 PR13155/BZ730884: ext3/jbd tracepoint listings A few tracepoint-class-specific hacks to make ext3 / jbd / ext4 / jbd2 all show up on appropriate kernels. * tapsets.cxx (tracepoint_extra_decls): Add extra ext[34] clauses. commit 0b9c887e33c06cb62bc21b99f7d9e18b6ca7f603 Author: Frank Ch. Eigler <fche@redhat.com> Date: Mon Oct 10 06:12:19 2011 -0400 testsuite: add dummyish test case for tracepoint listing only ----------------------------------------------------------------------- Summary of changes: tapsets.cxx | 9 ++++++--- testsuite/systemtap.base/tracepoints.exp | 3 ++- 2 files changed, 8 insertions(+), 4 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-10-10 10:22 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=20111010102238.8380.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).