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.3-375-g86518ac
Date: Thu, 09 Dec 2010 01:43:00 -0000	[thread overview]
Message-ID: <20101209014339.3972.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  86518ac521bab619698f36c3ec6fd1fe76a8d38b (commit)
       via  69f00416fb0ecb7ef5c0d6fbd7f57a8af38372f3 (commit)
       via  21e66313509549880f408421faf501f5c932014f (commit)
       via  79f640ac0196976988391fe7757a674961055f22 (commit)
       via  8d34b49dccef5bd17ce63a4c0a7bd6c342ad240f (commit)
       via  afb0ed885e5e185d22c1ba4b269575992f15d2bf (commit)
       via  24be3a0bf29054f7d8fdd9b25f6a7a458f205b15 (commit)
       via  94486feb6cce7b126f4c6e675efb7814c83fff7a (commit)
      from  669bf5e7d2fcb192e8fb9ca1b270fdae37915d1c (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 86518ac521bab619698f36c3ec6fd1fe76a8d38b
Author: William Cohen <wcohen@redhat.com>
Date:   Wed Dec 8 20:40:24 2010 -0500

    Edit tapset documentation comments
    
    Made the following changes to the documentation comments:
       - Remove the "General Syntax:" lines.
       - Remove trailing '.' for the summaries.
       - Make parameter information phrases rather than sentences

commit 69f00416fb0ecb7ef5c0d6fbd7f57a8af38372f3
Merge: 21e6631 669bf5e
Author: William Cohen <wcohen@redhat.com>
Date:   Wed Dec 8 20:39:48 2010 -0500

    Merge branch 'master' of ssh://sourceware.org/git/systemtap

commit 21e66313509549880f408421faf501f5c932014f
Author: William Cohen <wcohen@redhat.com>
Date:   Wed Dec 8 17:23:08 2010 -0500

    Edit the tapset documentation for conversions.stp
    
    Made the following changes to the documentation comments:
      - Remove the "General Syntax:" lines.
      - Remove trailing '.' for the summaries.

commit 79f640ac0196976988391fe7757a674961055f22
Author: William Cohen <wcohen@redhat.com>
Date:   Wed Dec 8 17:19:56 2010 -0500

    Edit the tapset documentation for conversions-guru.stp
    
    Made the following changes to the documentation comments:
      - Remove the "General Syntax:" lines.
      - Remove trailing '.' for the summaries.

commit 8d34b49dccef5bd17ce63a4c0a7bd6c342ad240f
Author: William Cohen <wcohen@redhat.com>
Date:   Wed Dec 8 17:16:12 2010 -0500

    Edit the tapset documentation for context-unwind.stp
    
    Made the following changes to the documentation comments:
      - Remove the "General Syntax:" lines.
      - Remove trailing '.' for the summaries.

commit afb0ed885e5e185d22c1ba4b269575992f15d2bf
Author: William Cohen <wcohen@redhat.com>
Date:   Wed Dec 8 17:12:14 2010 -0500

    Edit the tapset documentation for context-symbols.stp
    
    Made the following changes to the documentation comments:
      - Remove the "General Syntax:" lines.
      - Remove trailing '.' for the summaries and argumentation information.
      - Fix a few typos.

commit 24be3a0bf29054f7d8fdd9b25f6a7a458f205b15
Author: William Cohen <wcohen@redhat.com>
Date:   Wed Dec 8 17:06:21 2010 -0500

    Edit the tapset documentation for context.stp
    
    Made the following changes to the documentation comments:
      - Remove the "General Syntax:" lines.
      - Remove trailing '.' for the summaries.
      - Add title and description for cpuid function

commit 94486feb6cce7b126f4c6e675efb7814c83fff7a
Author: William Cohen <wcohen@redhat.com>
Date:   Wed Dec 8 16:51:43 2010 -0500

    Remove the "General Syntax:" lines from ansi.stp

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

Summary of changes:
 tapset/ansi.stp             |   26 -------
 tapset/context-symbols.stp  |   39 ++++-------
 tapset/context-unwind.stp   |   15 +----
 tapset/context.stp          |  119 +++++++------------------------
 tapset/conversions-guru.stp |   63 ++++++-----------
 tapset/conversions.stp      |   57 +++++----------
 tapset/ctime.stp            |    7 +--
 tapset/errno.stp            |    8 +--
 tapset/indent.stp           |    8 +--
 tapset/logging.stp          |   24 +++----
 tapset/memory.stp           |  164 +++++++++++++++++++++++--------------------
 tapset/pn.stp               |    4 +-
 tapset/string.stp           |   78 ++++++++-------------
 tapset/system.stp           |   10 +--
 tapset/task.stp             |  100 ++++++++++-----------------
 tapset/timestamp.stp        |    4 +-
 tapset/timestamp_gtod.stp   |   16 +---
 tapset/tokenize.stp         |    9 +--
 tapset/tzinfo.stp           |   15 +---
 tapset/uconversions.stp     |  157 ++++++++++++++---------------------------
 20 files changed, 320 insertions(+), 603 deletions(-)


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


                 reply	other threads:[~2010-12-09  1:43 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=20101209014339.3972.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).