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.3-308-gbf874c2
Date: Fri, 19 Nov 2010 20:46:00 -0000	[thread overview]
Message-ID: <20101119204614.1945.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  bf874c21db65c41a630a9d15a5683fb2be75d5fb (commit)
      from  93226a9188fc19b0f0179b30b04bafc245347c55 (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 bf874c21db65c41a630a9d15a5683fb2be75d5fb
Author: Frank Ch. Eigler <fche@elastic.org>
Date:   Fri Nov 19 15:43:01 2010 -0500

    testsuite: unembed test sources
    
    Pleading guilty to
    * youthful indiscretions
    * providing unadmirable examples
    
    Paying penance by
    * separating teeny little non-tcl sources from tcl code
    * swearing to do better in the future

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

Summary of changes:
 testsuite/systemtap.base/jennie.c    |    5 +++++
 testsuite/systemtap.base/uprobes.exp |   21 ++-------------------
 2 files changed, 7 insertions(+), 19 deletions(-)
 create mode 100644 testsuite/systemtap.base/jennie.c


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


                 reply	other threads:[~2010-11-19 20:46 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=20101119204614.1945.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).