From: "me at serhei dot io" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/28618] support non-capturing group & other features in stapregex
Date: Mon, 22 Nov 2021 20:36:32 +0000 [thread overview]
Message-ID: <bug-28618-6586-4bCrgFKE7v@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28618-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28618
--- Comment #1 from Serhei Makarov <me at serhei dot io> ---
commit 9e26507 implements the basic non-capturing group (?: ... ), will test
more thoroughly
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2021-11-22 20:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 20:13 [Bug translator/28618] New: support non-grouping match " me at serhei dot io
2021-11-22 20:13 ` [Bug translator/28618] support non-capturing group " me at serhei dot io
2021-11-22 20:36 ` me at serhei dot io [this message]
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=bug-28618-6586-4bCrgFKE7v@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@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).