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.8-254-g2c9bcc5 Date: Wed, 26 Sep 2012 17:44:00 -0000 [thread overview] Message-ID: <20120926174407.31317.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 2c9bcc5c4194914e57b768a3da047184940127db (commit) from 5c5f49c9a934ec4f39562cd253d5cb7eed762e8c (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 2c9bcc5c4194914e57b768a3da047184940127db Author: Frank Ch. Eigler <fche@redhat.com> Date: Wed Sep 26 13:41:54 2012 -0400 testsuite: set $SYSTEMTAP_SYNC For helping diagnose crashes that may occur during a testsuite, set $SYSTEMTAP_SYNC, which is handled by staprun, just before it does the module-insertion. This will make tests slower, sorry. * testsuite/Makefile.am (RUNTEST): Add env SYSTEMTAP_SYNC=yes. * testsuite/Makefile.in: Regenerated with love. ----------------------------------------------------------------------- Summary of changes: testsuite/Makefile.am | 2 +- testsuite/Makefile.in | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2012-09-26 17:44 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=20120926174407.31317.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).