Hi Jeremy, Jim and Tom,
while I do not think that Jeremy deliberately avoids contributions, his long-standing habit of tinkering on the kernel and shell in silence fails to motivate others to contribute or comment changes and keeps us in the dark about relevant improvements and bugfixes unless we actively "spy" on his commits via GIT. It is okay to not often do releases, but I would wish that he more often "thinks aloud" on the devel list, so we know what he is doing and share thoughts on it. For example the commit log tells that Jeremy has changed freecom env size config handling to allow as many chars as the docs had stated, in response to my analysis that signed int overflows made it support a few chars less. Yet he should have TALKED about that, also because Paul used that and long command line support (also updated, according to the git commit logs) and would surely have been happy to TEST the patched version. The 32k limit might also give a hint that OTHER apps may overflow if you use the full size, maybe a lower limit was safer? Meanwhile, not even the changelog text files in the ZIP of the source code download give a recent summary of the current command.com status and the kernel docs are not actually up to date either. So again: Jeremy, please share your thoughts more often, even if you have lost hope that people on freedos-devel will contribute kernel or shell patches. Unfortunately, after Pat's death in 2011, there has not really been a sufficient group effort to work on the kernel any more. Regards, Eric PS: Regarding the absence of file timestamps, I am sure somebody has figured out how to set them from GIT or SVN commit logs and has documented how to solve that issue? I would REALLY want correct per-file timestamps inside ZIP packages which I download for FreeDOS components. _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
