From: Enze Li <enze.li@hotmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
gdb-patches@sourceware.org, binutils@sourceware.org,
enze.li@gmx.com
Subject: Re: [PATCH] libctf: update regexp to allow makeinfo to build document
Date: Sat, 14 Jan 2023 12:36:41 +0800 [thread overview]
Message-ID: <OS3P286MB21526D7DC88F9F806AFF0DC7F0C39@OS3P286MB2152.JPNP286.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <83358ea17i.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 13 Jan 2023 10:44:36 -0500")
On Fri, Jan 13 2023 at 10:44:36 AM -0500, Eli Zaretskii wrote:
>> From: Andreas Schwab <schwab@linux-m68k.org>
>> Cc: Enze Li <enze.li@hotmail.com>, Eli Zaretskii <eliz@gnu.org>,
>> binutils@sourceware.org, enze.li@gmx.com
>> Date: Fri, 13 Jan 2023 16:36:09 +0100
>>
>> On Jan 13 2023, Eli Zaretskii via Gdb-patches wrote:
>>
>> > IMO, this solution has the same problem: it will stop working when
>> > Texinfo 10.1 will be released. I think the solution should be to use
>> >
>> > egrep 'texinfo[^0-9]*(6\.[3-9]|[7-9][0-9]?)'
>>
>> Since the match is not anchored, the trailing [0-9]? pattern is redundant.
>
> Right. But I now actually think we need something different, like
>
> egrep 'texinfo[^0-9]*(6\.[3-9]|[7-9]|[1-6][0-9])'
Hi Eli,
Thanks for your swift reply.
I've tested the following possible version numbers,
6.2.1, 6.3.1, 6.9.1, 7.0.1, 9.9.1, 10.1.1, 60.1.1, 199.1.1, 999.1.1
with the command like this:
$ echo "(GNU texinfo) 6.2" | \
egrep 'texinfo[^0-9]*(6\.[3-9]|[7-9]|[1-6][0-9])'
All of these tests are Okay.
I sent a new version to the list, ok for the trunk?
Best Regards,
Enze
next prev parent reply other threads:[~2023-01-14 4:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 14:42 Enze Li
2023-01-13 15:05 ` Eli Zaretskii
2023-01-13 15:36 ` Andreas Schwab
2023-01-13 15:44 ` Eli Zaretskii
2023-01-14 4:36 ` Enze Li [this message]
2023-01-14 7:36 ` Eli Zaretskii
2023-01-14 4:23 ` [PATCH v2] " Enze Li
2023-01-16 13:51 ` Nick Alcock
2023-01-16 15:19 ` Enze Li
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=OS3P286MB21526D7DC88F9F806AFF0DC7F0C39@OS3P286MB2152.JPNP286.PROD.OUTLOOK.COM \
--to=enze.li@hotmail.com \
--cc=binutils@sourceware.org \
--cc=eliz@gnu.org \
--cc=enze.li@gmx.com \
--cc=gdb-patches@sourceware.org \
--cc=schwab@linux-m68k.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).