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-0.9.7-46-g7c4e9d5
Date: Tue, 05 May 2009 16:09:00 -0000	[thread overview]
Message-ID: <20090505160954.18316.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  7c4e9d57761b10058d36756df3b39039e292812d (commit)
       via  5b8db791abb8c968b55fcf80380b8b7d8d77f53a (commit)
       via  fac37258fd3c7710407203b206963c7bff57075d (commit)
       via  2035bcd40b17832439df0a1eb28403b99a71b74f (commit)
      from  6820dda776595280e6dc535df32648b47d21e329 (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 7c4e9d57761b10058d36756df3b39039e292812d
Author: Dave Brolley <brolley@redhat.com>
Date:   Tue May 5 12:08:49 2009 -0400

    Describe new module signing capability.

commit 5b8db791abb8c968b55fcf80380b8b7d8d77f53a
Merge: fac37258fd3c7710407203b206963c7bff57075d 6820dda776595280e6dc535df32648b47d21e329
Author: Dave Brolley <brolley@redhat.com>
Date:   Tue May 5 11:56:37 2009 -0400

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

commit fac37258fd3c7710407203b206963c7bff57075d
Merge: 2035bcd40b17832439df0a1eb28403b99a71b74f 97d1fa6e24d8d4e8ceefc62f0d4a7f93a18e4125
Author: Dave Brolley <brolley@redhat.com>
Date:   Mon May 4 16:06:14 2009 -0400

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

commit 2035bcd40b17832439df0a1eb28403b99a71b74f
Author: Dave Brolley <brolley@redhat.com>
Date:   Mon May 4 16:05:22 2009 -0400

    Module signing and verification using a separate file for the module signature.

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

Summary of changes:
 Makefile.am                                |   18 +-
 Makefile.in                                |  157 +-
 NEWS                                       |    7 +
 aclocal.m4                                 |   60 +-
 buildrun.cxx                               |   11 +
 cache.cxx                                  |   50 +-
 config.in                                  |    3 +
 configure                                  | 4012 +++++++++++++---------------
 configure.ac                               |    3 +
 doc/Makefile.in                            |   18 +-
 doc/SystemTap_Tapset_Reference/Makefile.in |   20 +-
 grapher/Makefile.in                        |   20 +-
 main.cxx                                   |   22 +
 modsign.cxx                                |  554 ++++
 modsign.h                                  |    1 +
 nsscommon.c                                |   83 +
 nsscommon.h                                |    2 +
 runtime/staprun/mainloop.c                 |   10 +-
 runtime/staprun/modverify.c                |  389 +++
 runtime/staprun/modverify.h                |    8 +
 runtime/staprun/staprun_funcs.c            |  194 +-
 session.h                                  |    1 +
 stap-add-server-cert                       |   46 -
 stap-authorize-cert                        |   49 +
 stap-authorize-server-cert                 |   30 +
 stap-authorize-signing-cert                |   30 +
 stap-client                                |   84 +-
 stap-env                                   |   38 +
 stap-find-or-start-server                  |   16 +-
 stap-find-servers                          |   19 +-
 stap-gen-cert                              |   95 +
 stap-gen-server-cert                       |   93 -
 stap-server                                |   25 +-
 stap-server-connect.c                      |    2 +-
 stap-server.8.in                           |   43 +-
 stap-serverd                               |   54 +-
 stap-start-server                          |   10 +-
 systemtap.spec                             |   14 +-
 testsuite/Makefile.in                      |    5 +-
 testsuite/aclocal.m4                       |   36 +-
 testsuite/configure                        | 1224 ++++-----
 testsuite/lib/systemtap.exp                |    2 +
 util.cxx                                   |   21 +-
 util.h                                     |    1 +
 44 files changed, 4265 insertions(+), 3315 deletions(-)
 create mode 100644 modsign.cxx
 create mode 100644 modsign.h
 create mode 100644 nsscommon.c
 create mode 100644 nsscommon.h
 create mode 100644 runtime/staprun/modverify.c
 create mode 100644 runtime/staprun/modverify.h
 delete mode 100755 stap-add-server-cert
 create mode 100644 stap-authorize-cert
 create mode 100644 stap-authorize-server-cert
 create mode 100644 stap-authorize-signing-cert
 create mode 100644 stap-env
 create mode 100644 stap-gen-cert
 delete mode 100755 stap-gen-server-cert


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


                 reply	other threads:[~2009-05-05 16:09 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=20090505160954.18316.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).