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-300-gc997055
Date: Wed, 12 Oct 2011 15:16:00 -0000	[thread overview]
Message-ID: <20111012151607.8890.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  c99705558ffab82363ecbf0d1094fdf5ff4d5c94 (commit)
      from  9a1917ff9ec2165c896437e4bcab61d5c7dfd0fd (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 c99705558ffab82363ecbf0d1094fdf5ff4d5c94
Author: Mark Wielaard <mjw@redhat.com>
Date:   Wed Oct 12 12:53:30 2011 +0200

    Split translate dump_unwindsyms in separate collection/dump phases.
    
    Untangle separate module data collection. First collect all information,
    build-ids, symbols, unwind tables, etc. Put all collected info in the
    unwindsym_dump_context. Then dump it all out using the context.

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

Summary of changes:
 translate.cxx |  289 +++++++++++++++++++++++++++++++++++++++-----------------
 1 files changed, 201 insertions(+), 88 deletions(-)


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


                 reply	other threads:[~2011-10-12 15:16 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=20111012151607.8890.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).