public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: jistone@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.2-474-ge60bba4
Date: Mon, 12 Jul 2010 22:29:00 -0000	[thread overview]
Message-ID: <20100712222949.28299.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  e60bba4d31ea3763b4926b8eeda455d10b8877fc (commit)
      from  86e56b940fbdfd38fe12529e1a8428e31d2245c0 (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 e60bba4d31ea3763b4926b8eeda455d10b8877fc
Author: Josh Stone <jistone@redhat.com>
Date:   Mon Jul 12 15:05:40 2010 -0700

    Anchor bz10078.exp's regexp patterns
    
    If we are unlucky in buffering, then the test output could be read
    into expect as a single buffer.  Then one of our regexps could match the
    end of the buffer and consume the whole thing, even if we also wanted to
    match something earlier in the buffer.
    
    The solution is to anchor the patterns to the beginning of the buffer
    with '^', so we're sure to match everything we can.

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

Summary of changes:
 testsuite/systemtap.base/bz10078.exp |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)


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


                 reply	other threads:[~2010-07-12 22:29 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=20100712222949.28299.qmail@sourceware.org \
    --to=jistone@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).