public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: mark@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.6-303-g5921843
Date: Thu, 13 Oct 2011 11:58:00 -0000	[thread overview]
Message-ID: <20111013115810.26296.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  59218439d0e4dde4a9ccf289629099eed8c4f3ca (commit)
      from  bcc1790f75ce55fc27666f250c98e2522536d54f (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 59218439d0e4dde4a9ccf289629099eed8c4f3ca
Author: Mark Wielaard <mjw@redhat.com>
Date:   Thu Oct 13 13:53:08 2011 +0200

    PR13241 too much dump-unwindsyms processing for modules even if !need_symbols
    
    Introduce dump_section_list() that will pregenerate the section list when
    needed. dump_symbol_tables() now does the minimum necessary to extract
    the needed symbols, or will not even be called at all when !need_symbols
    and the module isn't the "kernel".

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

Summary of changes:
 translate.cxx |  284 ++++++++++++++++++++++++++++++++++++++-------------------
 1 files changed, 191 insertions(+), 93 deletions(-)


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


                 reply	other threads:[~2011-10-13 11:58 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=20111013115810.26296.qmail@sourceware.org \
    --to=mark@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).