Hi Arkady, why did you only mention in THIS mail what the MEANING of your patches is? You normally send a mail with subject like "patch: filename.c" and then there is ONLY the patch, zero explanation of any kind, nobody except you will know what you are trying to tell us and why your patch is supposed to improve things. So please 1. send some description along with the diff and 2. comment the changes in-line before you run diff and 3. tell us why the patch is good and whether you expect it to be good for all compilers or only for one certain compiler.
About Barts decision to take a break from FreeDOS kernel development: Could you please try to stabilize the current CVS version as 2034a release? I think it will be a long time to 2035 without you coordinating the changes, but as told "weeks ago", I agree with or at least accept your decision. Have fun "on the other side of the world". I assume you will stay linked to FreeDOS through the DOSEMU project. Eric. PS: Are you planning a MEM 1.7 release? Or does MEM even need a new maintainer? Do I have to figure out how to make EECHO use CON instead of BIOS or have you already found the answer to that problem yourself (being more experienced with information flow inside the kernel than most of us)? [In the "About Barts..." paragraph, "you" means "you, Bart". Was ambiguous...] ------------------------------------------------------- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 _______________________________________________ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
