public inbox for
help / color / mirror / Atom feed
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.8-40-g39b77cf
Date: Thu, 12 Jul 2012 20:38:00 -0000	[thread overview]
Message-ID: <> (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  39b77cffd8b9ebba6156f7b7f4db3ba505895568 (commit)
       via  b5477cd94d461909c5961b41970677c25a45910f (commit)
      from  3f803f9ee09362f0e77812859d43448e477780f5 (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 39b77cffd8b9ebba6156f7b7f4db3ba505895568
Author: Serguei Makarov <>
Date:   Thu Jul 12 16:35:35 2012 -0400

    PR14360: update testsuite to reflect new string-gluing behaviour.

commit b5477cd94d461909c5961b41970677c25a45910f
Author: Serguei Makarov <>
Date:   Thu Jul 12 16:27:38 2012 -0400

    PR14360, PR11207: clean up wildcard code in preparation for token-based macros.
    in parse.cxx:
    - get rid of ate_comment, enable "a" /* comment */ "b" string gluing
    - add ate_whitespace to keep track of token adjacency
    - restrict wildcard handling code to parse_probe_point()
      - this is now handled by keeping the component tokens of the wildcard
        separate, and gluing them together (conditional on adjacency)


Summary of changes:
 parse.cxx                         |   87 ++++++++++++++++++++++++------------
 testsuite/parseko/twentyseven.stp |    4 --
 testsuite/parseok/twentytwo.stp   |    4 ++
 3 files changed, 62 insertions(+), 33 deletions(-)
 delete mode 100755 testsuite/parseko/twentyseven.stp
 create mode 100755 testsuite/parseok/twentytwo.stp

systemtap: system-wide probe/trace tool

                 reply	other threads:[~2012-07-12 20:38 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).