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.7-299-g61598de
Date: Fri, 08 Jun 2012 17:35:00 -0000	[thread overview]
Message-ID: <20120608173512.4564.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  61598deb8717a45356b95b6028acbfb0f1fbb70d (commit)
       via  0c9f1e8515c8fbe79708954fd3dd5656fee304bb (commit)
       via  327a760e487f69c2d30f18558427ac9bec5abe98 (commit)
      from  7c3cb2d2a658e11f08feb9d7c1d20f56b5e496c8 (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 61598deb8717a45356b95b6028acbfb0f1fbb70d
Author: Frank Ch. Eigler <fche@redhat.com>
Date:   Fri Jun 8 13:31:09 2012 -0400

    docs: only use working xmlto --with-fop
    
    There are configurations in the wild that only endavour to work.
    
    * configure.ac: Re. fop, trust but VERIFY, with "xmlto --with-fop".

commit 0c9f1e8515c8fbe79708954fd3dd5656fee304bb
Author: Frank Ch. Eigler <fche@redhat.com>
Date:   Fri Jun 8 12:38:38 2012 -0400

    docs: tighten up generated tapset.pdf formatting
    
    Studying docbook-style-xsl in Fedora, and the corresponding xslt-fo
    stylesheets on the web, found some xsl:param options that make the
    tapsets.pdf a little more lean and a touch more mean.  See also
    http://snapshots.docbook.org/xsl/doc/fo/
    
    * doc/SystemTap_Tapset_Reference/Makefile.am: Pass some powerful
      stringparams to xmlto.

commit 327a760e487f69c2d30f18558427ac9bec5abe98
Author: Frank Ch. Eigler <fche@redhat.com>
Date:   Fri Jun 8 12:37:06 2012 -0400

    documentation: generate tapset reference pdf with fop if available
    
    * configure.ac: Look for fop program.  It runs much faster than
      pdfdblatex or whatnot.
    * doc/SystemTap_Tapset_Reference/Makefile.am: Pass --with-fop to
      xmlto if fop was found.

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

Summary of changes:
 Makefile.in                                      |    1 +
 configure                                        |   65 ++++++++++++++++++++++
 configure.ac                                     |   13 ++++
 doc/Makefile.in                                  |    1 +
 doc/SystemTap_Tapset_Reference/Makefile.am       |    9 +++-
 doc/SystemTap_Tapset_Reference/Makefile.in       |    6 ++-
 doc/SystemTap_Tapset_Reference/dummy-tapsets.xml |   37 ++++++++++++
 doc/beginners/Makefile.in                        |    1 +
 8 files changed, 131 insertions(+), 2 deletions(-)
 create mode 100644 doc/SystemTap_Tapset_Reference/dummy-tapsets.xml


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


                 reply	other threads:[~2012-06-08 17:35 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=20120608173512.4564.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).