Hi all, I saw you are planning a release for the end of the year and I'd like to contribute back and do a personal bug sprint until then. I am currently installing FreeDOS on my old MMX233-Laptop (on which I ported svgatextmode back to DOS [1] years ago :D), but I use dosemu as well.
Since I usually hack on the Linux Kernel, I am tuned to git-based workflows. I found git-repos at https://github.com/FDOS which are not mentioned in the docs/wiki but I assume they are official? So, I'd think the usual way is that I attach patches to bugs in the SF bugtracker. And if I find minor things on the way? I create new bug entries? Or patches to the list? I am fine with both. (For completeness, I wanted to have a look at #155, and just by glimpsing through FreeCom code, I found a typo in a string). And is there something like a release script for tools? Looking at bug #142 ("MODE command - can't set "STOP=2" ), the fix is really trivial and the patch is already there. Just the release missing. I am sure there is a script for that? Thanks, Wolfram [1] http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/util/user/svgatextmode_1_9_16rc1.txt
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
