Emacs 29.1 refers to the first release of Emacs 29, which has not yet occurred. Emacs 29.0.50 refers to version 29 of emacs which has not yet had a release candidate issued i.e. still very much development and not yet at beta level. Once the first release candidate is issued, the version will likely change to 29.0.90 and then once actually released, to 29.1.
Given that 29.0.50 at this point just means development version (and unless a commit hash is also included, head of the devel branch), you can assume the bug fix will be in 29.0.50 provided you have done a pull since that bug fix notice was posted. Daniel Ortmann <daniel.ortm...@oracle.com> writes: > FYI, > https://debbugs.gnu.org/cgi/bugreport.cgi?bug=57394 > > Lars at gnu says it is fixed in emacs 29 > The bug's web page says, more specifically, "bug marked as fixed in version > 29.1" > > ... I can't find emacs 29.1; my 'git pull' still says 29.0 and I don't see > any 29.1 branches available. > I have not been able to test and verify the fix. > > Thoughts? > > Daniel Ortmann <daniel.ortm...@oracle.com> writes: > > Error: error ("Eager macro-expansion failure: (void-function > byte-compile-warn-obsolete)") > debug-early-backtrace() > debug-early(error (error "Eager macro-expansion failure: > (void-function byte-compile-warn-obsolete)")) > > This should now be fixed in Emacs 29.