public inbox for
help / color / mirror / Atom feed
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.8-58-g16fc963
Date: Mon, 23 Jul 2012 16:34: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  16fc963fb861ac3ebbd83fd99076333aadb01ba1 (commit)
       via  2524d1fdc208f4cc8e3672a8b8d29af39eaea735 (commit)
      from  42f9c99b3f4d99e9c893f47b7b7fe74b6f0b3c59 (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 16fc963fb861ac3ebbd83fd99076333aadb01ba1
Author: Serguei Makarov <>
Date:   Mon Jul 23 12:30:46 2012 -0400

    PR11207 groundwork: lexer::scan() produces tok_junk instead of throwing errors.
    Handling parse_errors at scan time would get too complicated when there's
    a preprocessing stage between the lexer and parser (and it's no longer
    clear whether a given token will be used). Hence we produce specially marked
    tok_junk which store a message to use when the token is encountered at
    print_error() time.

commit 2524d1fdc208f4cc8e3672a8b8d29af39eaea735
Author: Serguei Makarov <>
Date:   Mon Jul 23 09:41:50 2012 -0400

    PR11207 groundwork: add a list of @words to check macro names against.


Summary of changes:
 parse.cxx |   99 ++++++++++++++++++++++++++++++++++++++++++++++++-------------
 parse.h   |    2 +
 2 files changed, 80 insertions(+), 21 deletions(-)

systemtap: system-wide probe/trace tool

                 reply	other threads:[~2012-07-23 16:34 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).