> Hi Jeremy, Jim and Tom,
Hi PerditionC,

> 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's ok to tinker in silence.

to release this is asshole behaviour. no excuses.


> 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.

I haven't gone into this too much as our contribution is no longer
relevant. but my *short source code* analysis says:
'if larger then 32535, then something small'. this might indeed be a
problem.


> Yet he should have TALKED about that,
yes.

> 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.
+1

> Unfortunately,
> after Pat's death in 2011, there has not really been a
> sufficient group effort to work on the kernel any more.

a fail to attribute ANY kernel effort to Pat after 2000.
How is this related to his (unfortunate) death?

> 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.
+1

'last time changed' timestamps were introduced for reason.

Tom



_______________________________________________
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to