public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: wcohen@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.7-324-g999250a
Date: Thu, 14 Jun 2012 16:06:00 -0000	[thread overview]
Message-ID: <20120614160558.12400.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  999250a6ec7a30e413183e1ab367a06188c39b9b (commit)
      from  b26de851945b98b58a206bda9c6d082921a54b36 (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 999250a6ec7a30e413183e1ab367a06188c39b9b
Author: William Cohen <wcohen@redhat.com>
Date:   Thu Jun 14 12:02:21 2012 -0400

    Update the Beginners Guide version information
    
    The "version:" flag in publican.cfg does not really work the way
    expected.  It will change the name of the generated pdf file during
    the build, but it does not completely override the <productnumber> in
    Book_Info.xml. Need manual fixing for the time being.

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

Summary of changes:
 doc/SystemTap_Beginners_Guide/en-US/Book_Info.xml |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)


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


                 reply	other threads:[~2012-06-14 16:06 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=20120614160558.12400.qmail@sourceware.org \
    --to=wcohen@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).