bug#60209: closed (29.0.50; [PATCH] lisp/progmodes/ruby-mode.el b/lisp/progmodes/ruby-mode.el)

[GNU bug Tracking System]

Your message dated Fri, 1 Sep 2023 21:58:47 +0200
with message-id 
<CADwFkmkFpUea94r690fMq3iVLVcPwPWqVMMDxqXORvWKOJrd0w@mail.gmail.com>
and subject line Re: bug#60209: 29.0.50; [PATCH] lisp/progmodes/ruby-mode.el 
b/lisp/progmodes/ruby-mode.el
has caused the debbugs.gnu.org bug report #60209,
regarding 29.0.50; [PATCH] lisp/progmodes/ruby-mode.el 
b/lisp/progmodes/ruby-mode.el
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
60209: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=60209
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems

--- Begin Message --- Subject: 29.0.50; [PATCH] lisp/progmodes/ruby-mode.el b/lisp/progmodes/ruby-mode.el Date: Mon, 19 Dec 2022 22:39:31 +0000

Hi,

I got a build error with last commit 2b1fdbffcb595bcd72fa9aa3db674c6985042bcb,

error ("Version must be a string")
  error("Version must be a string")
  version-to-list(29.1)
  version<(29.1 "19.29")
  #f(compiled-function (e1 e2) #<bytecode 0x7353c27725409c8>)((29.1
ruby-mode) ("19.29" time-stamp))

This patch will fix the error. Please merge it, thanks.

Best regards
Lin

0001-ruby-mode.el-fix-the-version-should-be-a-string.patch
Description: Text Data

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#60209: 29.0.50; [PATCH] lisp/progmodes/ruby-mode.el b/lisp/progmodes/ruby-mode.el
>
>
>
>
> Date: 
>
> Fri, 1 Sep 2023 21:58:47 +0200
>
>
>
>
> > I got a build error with last commit 2b1fdbffcb595bcd72fa9aa3db674c6985042bcb,
> >
> > error ("Version must be a string")
> >   error("Version must be a string")
> >   version-to-list(29.1)
> >   version<(29.1 "19.29")
> >   #f(compiled-function (e1 e2) #<bytecode 0x7353c27725409c8>)((29.1
> > ruby-mode) ("19.29" time-stamp))
> >
> > This patch will fix the error. Please merge it, thanks.
>
> Thanks for the patch, and sorry for the very late reply.
>
> This issue is already fixed on master, so I'm closing this bug.
>
>
> --- End Message ---