public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: serhei@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.7-293-g5fae6cc
Date: Thu, 07 Jun 2012 20:38:00 -0000	[thread overview]
Message-ID: <20120607203816.31728.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  5fae6ccbceb7a6524a84eecde86a1c1f43c38714 (commit)
       via  9e8a3699d7786185384819c90cd12fdb38dfbf6e (commit)
      from  5628061bad15195d4cafcdc27a9133c9131468dc (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 5fae6ccbceb7a6524a84eecde86a1c1f43c38714
Author: Serguei Makarov <smakarov@redhat.com>
Date:   Thu Jun 7 16:38:01 2012 -0400

    PR14208: Removed final few mentions of stapfuncs(3stap).

commit 9e8a3699d7786185384819c90cd12fdb38dfbf6e
Author: Serguei Makarov <smakarov@redhat.com>
Date:   Thu Jun 7 16:30:14 2012 -0400

    PR14208: Removed redundant old tapset manpages.

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

Summary of changes:
 HACKING                     |    9 +-
 doc/langref.tex             |    2 +-
 doc/tutorial.tex            |   10 +-
 man/tapset::iosched.3stap   |  100 ----
 man/tapset::irq.3stap       |  201 -------
 man/tapset::kprocess.3stap  |  106 ----
 man/tapset::netdev.3stap    |   77 ---
 man/tapset::nfs.3stap       | 1236 -------------------------------------------
 man/tapset::nfsd.3stap      |  513 ------------------
 man/tapset::pagefault.3stap |   40 --
 man/tapset::perf.3stap      |   84 ---
 man/tapset::rpc.3stap       |  583 --------------------
 man/tapset::scsi.3stap      |  151 ------
 man/tapset::signal.3stap    |  509 ------------------
 man/tapset::snmp.3stap      |  138 -----
 man/tapset::socket.3stap    |  485 -----------------
 man/tapset::tcp.3stap       |  102 ----
 man/tapset::udp.3stap       |  102 ----
 18 files changed, 14 insertions(+), 4434 deletions(-)
 delete mode 100644 man/tapset::iosched.3stap
 delete mode 100644 man/tapset::irq.3stap
 delete mode 100644 man/tapset::kprocess.3stap
 delete mode 100644 man/tapset::netdev.3stap
 delete mode 100644 man/tapset::nfs.3stap
 delete mode 100644 man/tapset::nfsd.3stap
 delete mode 100644 man/tapset::pagefault.3stap
 delete mode 100644 man/tapset::perf.3stap
 delete mode 100644 man/tapset::rpc.3stap
 delete mode 100644 man/tapset::scsi.3stap
 delete mode 100644 man/tapset::signal.3stap
 delete mode 100644 man/tapset::snmp.3stap
 delete mode 100644 man/tapset::socket.3stap
 delete mode 100644 man/tapset::tcp.3stap
 delete mode 100644 man/tapset::udp.3stap


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


                 reply	other threads:[~2012-06-07 20:38 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=20120607203816.31728.qmail@sourceware.org \
    --to=serhei@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).