public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: eugen@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-0.9-17-ga9c4836 Date: Sat, 21 Feb 2009 19:59:00 -0000 [thread overview] Message-ID: <20090221195944.28772.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 a9c48361fbd78af46fdc36bc36ca8c6c8371de0c (commit) from 60708c55af46b7e42392e0d679df85a824d71b45 (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 a9c48361fbd78af46fdc36bc36ca8c6c8371de0c Author: Eugeniy Meshcheryakov <eugen@debian.org> Date: Sat Feb 21 20:59:24 2009 +0100 make all examples executable ----------------------------------------------------------------------- Summary of changes: 0 files changed, 0 insertions(+), 0 deletions(-) mode change 100644 => 100755 testsuite/systemtap.examples/interrupt/scf.stp mode change 100644 => 100755 testsuite/systemtap.examples/io/iostats.stp mode change 100644 => 100755 testsuite/systemtap.examples/memory/pfaults.stp mode change 100644 => 100755 testsuite/systemtap.examples/network/tcp_connections.stp mode change 100644 => 100755 testsuite/systemtap.examples/profiling/latencytap.stp mode change 100644 => 100755 testsuite/systemtap.examples/profiling/timeout.stp mode change 100644 => 100755 testsuite/systemtap.examples/profiling/topsys.stp hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2009-02-21 19:59 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=20090221195944.28772.qmail@sourceware.org \ --to=eugen@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).