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.4-142-g03c4129
Date: Tue, 08 Mar 2011 16:45:00 -0000	[thread overview]
Message-ID: <20110308164542.30174.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  03c412911eeb0f737738286878ddad12fb075f97 (commit)
       via  b176e844ed67c5775d201d135abfac90ae12e892 (commit)
       via  c1abd6ae4de1d5f15e892c2eae97608268e47b4e (commit)
      from  d54a65f603da4bdb62ccc5586cee8fa623a4535f (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 03c412911eeb0f737738286878ddad12fb075f97
Merge: b176e84 d54a65f
Author: Dave Brolley <brolley@redhat.com>
Date:   Tue Mar 8 11:42:50 2011 -0500

    Merge branch 'master' of ssh://sourceware.org/git/systemtap
    
    Conflicts:
    	runtime/staprun/configure

commit b176e844ed67c5775d201d135abfac90ae12e892
Author: Dave Brolley <brolley@redhat.com>
Date:   Tue Mar 8 11:38:55 2011 -0500

    PR 12543 - PKGLIBEXECDIR undefined, causing uprobes.ko build to fail
    
    Always substitute the correct path for PKGLIBEXECDIR in client/server cert
    management scripts when installing; not just when --enable-server is
    configured.

commit c1abd6ae4de1d5f15e892c2eae97608268e47b4e
Author: Dave Brolley <brolley@redhat.com>
Date:   Tue Mar 8 11:36:56 2011 -0500

    PR 12540 - Could not obtain information on password file
    
    While building uprobes.ko. Ensure that the required tools and resources
    are in place before attempting to digitaly sign the uprobes.ko module.

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

Summary of changes:
 Makefile.am                                |    2 -
 Makefile.in                                |   21 +-
 aclocal.m4                                 |   40 ++--
 configure                                  |  451 +++++++++++++---------------
 doc/Makefile.in                            |    2 -
 doc/SystemTap_Tapset_Reference/Makefile.in |    2 -
 doc/beginners/Makefile.in                  |    2 -
 grapher/Makefile.in                        |    2 -
 pcp/configure                              |  338 +++++++++++----------
 runtime/staprun/Makefile.in                |    2 -
 runtime/staprun/aclocal.m4                 |   40 ++--
 runtime/staprun/configure                  |  294 ++++++++----------
 runtime/uprobes/Makefile                   |   27 ++-
 testsuite/aclocal.m4                       |    4 +-
 testsuite/configure                        |  226 +++++++--------
 15 files changed, 694 insertions(+), 759 deletions(-)


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


                 reply	other threads:[~2011-03-08 16:45 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=20110308164542.30174.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).