Hi Tom, Correction!
> On Nov 1, 2024, at 3:25 PM, Jerome Shidel via Freedos-user > <freedos-user@lists.sourceforge.net> wrote: > > Hi Tom > >>> On the other hand, the unstable branch of FreeCOM contains a test version >>> of the command shell which is using the same version number as the previous >>> shell. >> >> so we have some unchanged and some changed version of freecom, both by the >> same number. > > Yes, sort-of… > > Like the kernel, the most recent official release of FreeCOM was 0.85a > released back in 2021. > > There has not been a more recent official release. > > However, for testing purposes, I was able to coerce a copy of a build that > included many of the more recent patches and bug fixes. Since, this was not > an “official” release, it was not assigned a new version number. Sorry, I was wrong. I did not put the “other” “unofficial” build of FreeCOM into the GitLab Archive. It was something I tested locally to see if some of the bugs reported locally. Not being an official test version, the build I was able to acquired was not placed in the unstable branch for general testing. Because it was not an official test build, I think that actually makes sense to me. I do not know why I though I had uploaded it. So, like the kernel. The version of FreeCOM in the GitLab Archive unstable branch (and on the Interim Test Builds) was the same as the one provided in FreeDOS 1.3. I realized this while I was going through and merging the different projects that have unstable branches into their master branches. I apologize for my error. :-) Jerome _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
