public inbox for
help / color / mirror / Atom feed
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.7-266-g143cad5
Date: Fri, 25 May 2012 19:04:00 -0000	[thread overview]
Message-ID: <> (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  143cad54e2e5ea21379aab1fb0736c13f7850e06 (commit)
       via  ca5b4d2ec92e12eed8acfe50911236cba26d0ae4 (commit)
      from  e8474d2aac689025e8e540fa27ec68088bc5e468 (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 143cad54e2e5ea21379aab1fb0736c13f7850e06
Merge: ca5b4d2 e8474d2
Author: Serguei Makarov <>
Date:   Fri May 25 15:04:01 2012 -0400

    Merge branch 'master' of

commit ca5b4d2ec92e12eed8acfe50911236cba26d0ae4
Author: Serguei Makarov <>
Date:   Fri May 25 14:57:58 2012 -0400

    PR14146: adapted to produce passable tapset::* manpages.
    The resulting manpages can act as 'very succinct' (read: utterly
    bare-bones) tables of contents listing documented functions and probes,
    and referring the user to probe::* and function::* manpages generated by
    the 'robust' (read: hideously complicated and slow, but very reliable)
    DocBook toolchain. is currently not hooked up to the build sequence, pending
    delivery of a fresh supply of fingers to cross in hope that everything
    works as advertised.


Summary of changes:
 doc/SystemTap_Tapset_Reference/ |  109 ++++++++++++++++++++++++++++
 doc/Tapset_Reference_Guide/     |    4 +-
 2 files changed, 112 insertions(+), 1 deletions(-)
 create mode 100755 doc/SystemTap_Tapset_Reference/

systemtap: system-wide probe/trace tool

                 reply	other threads:[~2012-05-25 19:04 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).