public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: brolley@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.0-259-g7067e1b
Date: Tue, 24 Nov 2009 19:53:00 -0000	[thread overview]
Message-ID: <20091124195301.798.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  7067e1b0418eed528fe2d102654dbe12bb9236af (commit)
       via  37f1e3c413aee81f7590de431d232a474eb412ee (commit)
      from  90bba7158de040705a101ba1fdf6062866b4b4e9 (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 7067e1b0418eed528fe2d102654dbe12bb9236af
Merge: 37f1e3c413aee81f7590de431d232a474eb412ee 90bba7158de040705a101ba1fdf6062866b4b4e9
Author: Dave Brolley <brolley@redhat.com>
Date:   Tue Nov 24 14:51:46 2009 -0500

    Merge branch 'master' of ssh://sources.redhat.com/git/systemtap

commit 37f1e3c413aee81f7590de431d232a474eb412ee
Author: Dave Brolley <brolley@redhat.com>
Date:   Tue Nov 24 14:50:28 2009 -0500

    PR 10976, 10984. Loading of signed modules (script module and uprobes) limited to members of stapusr.

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

Summary of changes:
 runtime/staprun/staprun_funcs.c |  182 ++++++++++++++++++++++++++-------------
 1 files changed, 121 insertions(+), 61 deletions(-)


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


                 reply	other threads:[~2009-11-24 19:53 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=20091124195301.798.qmail@sourceware.org \
    --to=brolley@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).