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.3-121-gc807ba1
Date: Fri, 10 Sep 2010 18:21:00 -0000	[thread overview]
Message-ID: <20100910182153.25332.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  c807ba1b59a653d54b53155da64444b0db0beb7c (commit)
      from  dadb3ad90b6f9df1ec1e7ca132a1c682fb93303c (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 c807ba1b59a653d54b53155da64444b0db0beb7c
Author: Dave Brolley <brolley@redhat.com>
Date:   Fri Sep 10 14:18:07 2010 -0400

    PR 11905: Take more care with stap-server config files.
    
    - Config files now have a fixed suffix which avoids collisions with other
      stap-server files.
    - Config files are now interpreted in order to avoid execution of random
      code.

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

Summary of changes:
 Makefile.in                       |    7 +-
 configure                         |    3 +-
 configure.ac                      |    1 +
 stap-server                       |  558 +++++++++++++++++++++++--------------
 stap-server.8 => stap-server.8.in |   64 +++--
 stap-serverd                      |  110 ++++----
 6 files changed, 447 insertions(+), 296 deletions(-)
 rename stap-server.8 => stap-server.8.in (84%)


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


                 reply	other threads:[~2010-09-10 18:21 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=20100910182153.25332.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).