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, master, updated. release-1.7-53-gb88df28
Date: Mon, 27 Feb 2012 18:56:00 -0000	[thread overview]
Message-ID: <20120227185644.30154.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  b88df28c5a23aa31f4453aaaf1c2eb232cb8d99e (commit)
      from  d5c4314752317f83c092fd56357d66a9273acc93 (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 b88df28c5a23aa31f4453aaaf1c2eb232cb8d99e
Author: David Smith <dsmith@redhat.com>
Date:   Mon Feb 27 12:56:29 2012 -0600

    Fix PR13646 (partial) by adding IPv6 support to tcp.sendmsg/tcp.disconnect.
    
    * tapset/tcp.stp (tcp.sendmsg): Added 'family' member.
      (tcp.disconnect): Ditto.
    * testsuite/buildok/tcp-detailed.stp: Added tests for new 'family'
      members.

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

Summary of changes:
 tapset/tcp.stp                     |    4 ++++
 testsuite/buildok/tcp-detailed.stp |    4 ++--
 2 files changed, 6 insertions(+), 2 deletions(-)


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


                 reply	other threads:[~2012-02-27 18:56 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=20120227185644.30154.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).