public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: mark@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.0-499-gb86c336
Date: Wed, 13 Jan 2010 14:14:00 -0000	[thread overview]
Message-ID: <20100113141423.3695.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  b86c3365b3c8ca6e6e459d07de124b7ba2d66cad (commit)
      from  e25ab03ca60a5c6ca687b698502730ba2ad244dc (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 b86c3365b3c8ca6e6e459d07de124b7ba2d66cad
Author: Mark Wielaard <mjw@redhat.com>
Date:   Wed Jan 13 15:11:58 2010 +0100

    Faulty conditionals are parse errors, not semantical errors.
    
    The test was correct, the given construct should fail. But it fails because
    it is a parse error, not because it is a semantical error. So move into the
    right pass1-4 sub-directory.
    
    * testsuite/semko/conditional.stp: Moved to...
    * testsuite/parseko/conditional.stp: ... here.

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

Summary of changes:
 testsuite/{semko => parseko}/conditional.stp |    0
 1 files changed, 0 insertions(+), 0 deletions(-)
 rename testsuite/{semko => parseko}/conditional.stp (100%)


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


                 reply	other threads:[~2010-01-13 14:14 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=20100113141423.3695.qmail@sourceware.org \
    --to=mark@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).