From: "Martin Liška" <mliska@suse.cz>
To: Hans-Peter Nilsson <hp@axis.com>, Mike Stump <mikestump@comcast.net>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: Ping: [PATCH 1/2] testsuite: Provide means to regexp in multiline patterns
Date: Tue, 7 Mar 2023 15:34:14 +0100 [thread overview]
Message-ID: <863a2969-d242-9dd0-e0cb-2582c0997973@suse.cz> (raw)
In-Reply-To: <20230307003213.B90CC20405@pchp3.se.axis.com>
On 3/7/23 01:32, Hans-Peter Nilsson wrote:
>> From: Mike Stump <mikestump@comcast.net>
>> Date: Mon, 6 Mar 2023 02:05:35 -0800
>
>> Ok
>
> Thanks! The server-side hook didn't like my ChangeLog
> entry:
>
> * lib/multiline.exp (_build_multiline_regex): Map
> "{re:" to "(", ":re}" to ")" and ":re?}" to ")?".
>
> It seems I forgot to validate that patch by
> contrib/gcc-changelog/git_check_commit.py, which complains:
>
> Checking c0debd6f586ef76f1ceabfed11d7eaf8f6d1b110: FAILED
> ERR: bad wrapping of parenthesis: " "{re:" to "(", ":re}" to ")" and ":re?}" to ")?"."
Hello.
Yeah, that's quite interesting problem ;)
>
> I gave in and took the easy way out; not fixing the bug in
> that script, but instead "wrapped the parenthesis" to:
>
> * lib/multiline.exp (_build_multiline_regex): Map
> "{re:" to "(", similarly ")?" from ":re?}" and the
> same without question mark.
>
> I hope to make amends by fixing git_check_commit.py, if
> given guidance.
Sure, you can take a look at:
contrib/gcc-changelog/git_commit.py::process_parentheses
where we might want to skip the stack push/pop if the character is wrapper
in apostrophes or double quotes.
Martin
>
> brgds, H-P
prev parent reply other threads:[~2023-03-07 14:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 19:16 Hans-Peter Nilsson
2023-03-04 1:58 ` Ping: " Hans-Peter Nilsson
2023-03-06 10:05 ` Mike Stump
2023-03-07 0:32 ` Hans-Peter Nilsson
2023-03-07 14:34 ` Martin Liška [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=863a2969-d242-9dd0-e0cb-2582c0997973@suse.cz \
--to=mliska@suse.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=hp@axis.com \
--cc=mikestump@comcast.net \
/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).