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-650-g132b6fe
Date: Fri, 23 Dec 2011 19:51:00 -0000	[thread overview]
Message-ID: <20111223195111.13179.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  132b6fe86650df9cd1c684d133d7f815512cb519 (commit)
       via  80de107ea9a9d1509ecfe188eadf0be2284c7420 (commit)
      from  68e60a385a783dd0159b0342f61069a2909d4fe8 (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 132b6fe86650df9cd1c684d133d7f815512cb519
Author: Frank Ch. Eigler <fche@redhat.com>
Date:   Fri Dec 23 14:49:56 2011 -0500

    $SYSTEMTAP_SYNC: new environment variable for staprun
    
    If set, it runs a sync(2) before the stap init_module(2)s.  This is
    only for helping bring up stap on unstable environments, so is not
    formally documented.

commit 80de107ea9a9d1509ecfe188eadf0be2284c7420
Author: Frank Ch. Eigler <fche@redhat.com>
Date:   Fri Dec 23 14:38:15 2011 -0500

    stap-report: include CONFIG_MODULE_* items too

-----------------------------------------------------------------------

Summary of changes:
 runtime/staprun/staprun_funcs.c |    4 ++++
 stap-report                     |    2 +-
 2 files changed, 5 insertions(+), 1 deletions(-)


hooks/post-receive
--
systemtap: system-wide probe/trace tool


                 reply	other threads:[~2011-12-23 19:51 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=20111223195111.13179.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: link
Be 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).