You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The reason will be displayed to describe this comment to others. Learn more.
Btw, do you happen to know what is
freedos-20? I wanted to fill a ticket on
their SF, and it has freedos-20 there,
although I can't find such repo on their
servers.
The reason will be displayed to describe this comment to others. Learn more.
I don't think it exists. It's often been touted as the next big release, but from what I see there's only incremental development in FreeDOS. Tickets should be raised either in github/fdos projects if they are specific to the projects that exist there, or in the massive gitlab based project. I never tend to look at Sourceforge tickets, mainly because they never get closed and it's anybody's guess if the problem still exists.
On Wed, 01 Jan 2025 04:55:25 -0800 Stas Sergeev ***@***.***> wrote:
Btw, do you happen to know what is
freedos-20? I wanted to fill a ticket on
their SF, and it has freedos-20 there,
although I can't find such repo on their
servers.
--
Reply to this email directly or view it on GitHub:
5045c71#commitcomment-150849450
You are receiving this because you commented.
Message ID: ***@***.***>
The reason will be displayed to describe this comment to others. Learn more.
The ticket I filled is that they do not
populate C:\LINKS in most of their
packages. In fact, from the packages
that we install, only Gopherus puts
its bat file into links, so other apps
can't be run by PATH.
Such a report probably didn't suit
any of their github repos.
Среда, 1 января 2025 г получено от Andrew Bird:
I don't think it exists. It's often been touted as the next big release, but from what I see there's only incremental development in FreeDOS. Tickets should be raised either in github/fdos projects if they are specific to the projects that exist there, or in the massive gitlab based project. I never tend to look at Sourceforge tickets, mainly because they never get closed and it's anybody's guess if the problem still exists.
On Wed, 01 Jan 2025 04:55:25 -0800
Stas Sergeev ***@***.***> wrote:
> Btw, do you happen to know what is
> freedos-20? I wanted to fill a ticket on
> their SF, and it has freedos-20 there,
> although I can't find such repo on their
> servers.
>
> --
> Reply to this email directly or view it on GitHub:
> 5045c71#commitcomment-150849450
> You are receiving this because you commented.
>
> Message ID: ***@***.***>
--
Reply to this email directly or view it on GitHub:
5045c71#commitcomment-150849554
You are receiving this because you authored the thread.
Message ID: ***@***.***
5045c71
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You may want to re-enable the Github Actions scheduled CI test, it was disabled due to 60 days of inactivity.
5045c71
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done, thanks.
5045c71
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Btw, do you happen to know what is
freedos-20? I wanted to fill a ticket on
their SF, and it has freedos-20 there,
although I can't find such repo on their
servers.
5045c71
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
5045c71
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.