public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: fche@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.3-287-g7c7b1cd
Date: Wed, 10 Nov 2010 16:59:00 -0000	[thread overview]
Message-ID: <20101110165904.28219.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  7c7b1cd59e2ab802efa9c200699e8fc3adfca0ac (commit)
       via  6b72655f649e8226f6b1258c95f08678c441c0f1 (commit)
       via  8be729ac6f8e1d56a2fdcbb0c7c3fd9a1828cb5b (commit)
       via  3abb860fcfbf5d5211501b1058cff108c1b766cf (commit)
      from  e090a368a7b283a3efe4ea3beca0667fdf64d1d3 (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 7c7b1cd59e2ab802efa9c200699e8fc3adfca0ac
Author: Frank Ch. Eigler <fche@elastic.org>
Date:   Wed Nov 10 11:57:43 2010 -0500

    runtime: tolerate overlong section/symbol names better
    
    * runtime/staprun/staprun.c (send_a_relocation): Don't
      complain about overlong names, except if very verbose.
      Triple-check null termination of surviving strings.

commit 6b72655f649e8226f6b1258c95f08678c441c0f1
Author: Frank Ch. Eigler <fche@elastic.org>
Date:   Wed Nov 10 11:22:18 2010 -0500

    releng: tweak build ordering to get code first, docs last
    
    * Makefile.am (SUBDIRS): Build . and runtime/staprun first.
    * Makefile.in: Regenerated.

commit 8be729ac6f8e1d56a2fdcbb0c7c3fd9a1828cb5b
Author: Frank Ch. Eigler <fche@elastic.org>
Date:   Wed Nov 10 11:21:38 2010 -0500

    regen misc. Makefile.in's due to earlier addition of support_section_question

commit 3abb860fcfbf5d5211501b1058cff108c1b766cf
Author: Frank Ch. Eigler <fche@elastic.org>
Date:   Wed Nov 10 11:13:26 2010 -0500

    runtime: bump up module/symbol name length limits
    
    Due to a report that kernel modules written with C++ inside sometimes
    grow extra-long sections:
    
    * runtime/transport/transport_msgs.h: Double
      STP_MODULE_NAME_LEN and STP_SYMBOL_NAME_LEN to 128.

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

Summary of changes:
 Makefile.am                                |    2 +-
 Makefile.in                                |    2 +-
 doc/Makefile.in                            |    1 +
 doc/SystemTap_Tapset_Reference/Makefile.in |    1 +
 doc/beginners/Makefile.in                  |    1 +
 grapher/Makefile.in                        |    1 +
 runtime/staprun/staprun.c                  |   18 +++++++++++-------
 runtime/transport/transport_msgs.h         |    4 ++--
 8 files changed, 19 insertions(+), 11 deletions(-)


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


                 reply	other threads:[~2010-11-10 16:59 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=20101110165904.28219.qmail@sourceware.org \
    --to=fche@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).