public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: dsmith@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, pr7043, updated. release-0.9.7-148-g01adca5
Date: Wed, 03 Jun 2009 18:06:00 -0000	[thread overview]
Message-ID: <20090603180614.2741.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, pr7043 has been updated
       via  01adca5bca8d61e3fdf09017496deec8859fe12d (commit)
      from  a655ff03c59722c229a40909d0de9e3dfe63483e (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 01adca5bca8d61e3fdf09017496deec8859fe12d
Author: David Smith <dsmith@redhat.com>
Date:   Wed Jun 3 13:04:54 2009 -0500

    Fixed STP_TRANSPORT_VERSION 1 behavior.
    * runtime/transport/control.c (_stp_ctl_write_dbug): Added support for
      more messages.
    * runtime/transport/relay_v2.c (_stp_transport_data_fs_start): New
      function.
      (_stp_transport_data_fs_stop): Ditto.
      (_stp_transport_data_fs_close): Moved some functionality into
      _stp_transport_data_fs_stop() and calls _stp_transport_data_fs_stop()
      also.
      (_stp_transport_data_fs_init): Moved some functionality into
      _stp_transport_data_fs_start() and calls _stp_transport_data_fs_start()
      also.
    * runtime/transport/relayfs.c (_stp_transport_data_fs_start): New
      function.
      (_stp_transport_data_fs_stop): Ditto.
      (_stp_transport_data_fs_close): Moved some functionality into
      _stp_transport_data_fs_stop() and calls _stp_transport_data_fs_stop()
      also.
      (_stp_transport_data_fs_init): Moved some functionality into
      _stp_transport_data_fs_start() and calls _stp_transport_data_fs_start()
      also.
    * runtime/transport/ring_buffer.c (_stp_transport_data_fs_start): New
      empty function.
      (_stp_transport_data_fs_stop): Ditto.
    * runtime/transport/transport.h: Added _stp_transport_data_fs_start() and
      _stp_transport_data_fs_stop() prototypes.
    * runtime/transport/transport.c (_stp_cleanup_and_exit): Calls
      _stp_transport_data_fs_stop().
      (_stp_transport_close): Calls _stp_transport_fs_close() earlier.
      (_stp_transport_init): Calls _stp_transport_data_fs_start().

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

Summary of changes:
 runtime/transport/control.c     |   18 ++++++++++++++++++
 runtime/transport/relay_v2.c    |   29 +++++++++++++++++++++--------
 runtime/transport/relayfs.c     |   26 ++++++++++++++++++++------
 runtime/transport/ring_buffer.c |   10 ++++++++++
 runtime/transport/transport.c   |   13 ++++---------
 runtime/transport/transport.h   |   14 ++++++++++++++
 6 files changed, 87 insertions(+), 23 deletions(-)


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


                 reply	other threads:[~2009-06-03 18:06 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=20090603180614.2741.qmail@sourceware.org \
    --to=dsmith@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).