From: Kris Van Hees <kris.van.hees@oracle.com>
To: Kris Van Hees <kris.van.hees@oracle.com>
Cc: eugene.loh@oracle.com, dtrace@lists.linux.dev,
dtrace-devel@oss.oracle.com
Subject: Re: [PATCH 1/2] Support deeper version numbers (e.g. 2.0.4.x)
Date: Tue, 27 Jan 2026 11:33:51 -0500 [thread overview]
Message-ID: <aXjo7yTmrpxJzvJk@oracle.com> (raw)
In-Reply-To: <aXgScYsIu94O/Me3@oracle.com>
On Mon, Jan 26, 2026 at 08:18:41PM -0500, Kris Van Hees wrote:
> On Mon, Jan 26, 2026 at 06:41:49PM -0500, eugene.loh@oracle.com wrote:
> > From: Eugene Loh <eugene.loh@oracle.com>
> >
> > Signed-off-by: Eugene Loh <eugene.loh@oracle.com>
>
> Reviewed-by: Kris Van Hees <kris.van.hees@oracle.com>
Woops, I was too hasty on this. More changes are needed... See the following:
if (current) {
$0 = versions[idx[n]];
if ($3 == 0)
printf "%s.%s", $1, $2;
else
printf "%s.%s.%s", $1, $2, $3;
exit(0);
}
Obviously, we need to account here also for the possibility of 4 digits, and
then again in all the other places where we output version numbers.
> > ---
> > libdtrace/mkvers | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/libdtrace/mkvers b/libdtrace/mkvers
> > index 6f9240320..087c09169 100755
> > --- a/libdtrace/mkvers
> > +++ b/libdtrace/mkvers
> > @@ -10,7 +10,7 @@
> > NF == 0 { next; }
> >
> > {
> > - if (match($1, /^[1-9][0-9]*(\.[0-9]*){1,2}$/) == 0) {
> > + if (match($1, /^[1-9][0-9]*(\.[0-9]*){1,3}$/) == 0) {
> > print "E: Invalid version string: " $1 >"/dev/stderr";
> > exit 1
> > }
> > --
> > 2.47.3
> >
next prev parent reply other threads:[~2026-01-27 16:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 23:41 [PATCH 1/2] Support deeper version numbers (e.g. 2.0.4.x) eugene.loh
2026-01-26 23:41 ` [PATCH 2/2] Update NEWS and dtrace.spec for release 2.0.4.1 eugene.loh
2026-01-27 1:20 ` Kris Van Hees
2026-01-27 1:18 ` [PATCH 1/2] Support deeper version numbers (e.g. 2.0.4.x) Kris Van Hees
2026-01-27 16:33 ` Kris Van Hees [this message]
2026-01-27 16:38 ` Kris Van Hees
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=aXjo7yTmrpxJzvJk@oracle.com \
--to=kris.van.hees@oracle.com \
--cc=dtrace-devel@oss.oracle.com \
--cc=dtrace@lists.linux.dev \
--cc=eugene.loh@oracle.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.