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.6-517-g72dd064 Date: Tue, 29 Nov 2011 21:32:00 -0000 [thread overview] Message-ID: <20111129213230.12085.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 72dd064de16fe530bd16ba4622dcb16effbfc361 (commit) from 3a85fccd0f9a41e90fefeda0f114b19f5acd38ec (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 72dd064de16fe530bd16ba4622dcb16effbfc361 Author: Frank Ch. Eigler <fche@redhat.com> Date: Tue Nov 29 16:29:09 2011 -0500 PR13458: laugh in the face of xslt Using a dozen-line xslt script, one can sort the generated tapsets.xml documentation's reference sections. Thank you interwebs: http://stackoverflow.com/questions/572854/how-to-sort-a-subelement-of-xml-with-xslt http://www.w3schools.com/xpath/xpath_syntax.asp ----------------------------------------------------------------------- Summary of changes: doc/SystemTap_Tapset_Reference/Makefile.am | 8 +++++--- doc/SystemTap_Tapset_Reference/Makefile.in | 8 +++++--- doc/SystemTap_Tapset_Reference/sort-tapsets.xslt | 21 +++++++++++++++++++++ 3 files changed, 31 insertions(+), 6 deletions(-) create mode 100644 doc/SystemTap_Tapset_Reference/sort-tapsets.xslt hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-11-29 21:32 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=20111129213230.12085.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: linkBe 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).