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-287-g4f81096
Date: Thu, 07 Jun 2012 14:52:00 -0000	[thread overview]
Message-ID: <20120607145250.10852.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  4f810968721341d37aa1bcc30c4d9d7158da79f8 (commit)
      from  e19ebcf70ab20d61d845d67f1d82352891f404e0 (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 4f810968721341d37aa1bcc30c4d9d7158da79f8
Author: Frank Ch. Eigler <fche@redhat.com>
Date:   Thu Jun 7 10:50:42 2012 -0400

    testsuite check.exp: tolerate relative $srcdir
    
    After commit c66be968a4ea, the testsuite could receive a relative
    $srcdir (if the systemtap build tree was configured with a relative
    source tree).  check.exp was not prepared for this, switching around
    the cwd's, and still using relative path name strings.  So now we
    change directories more circumspectly.  Isly thatly anly adverbly?

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

Summary of changes:
 testsuite/systemtap.examples/check.exp |   22 ++++++++++++----------
 1 files changed, 12 insertions(+), 10 deletions(-)


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


                 reply	other threads:[~2012-06-07 14:52 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=20120607145250.10852.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).