[Documentation] Implemented / Not Implemented commands?

[rubyFeedback]

Hey there,

You provide a listing of entries that are currently not finished, aka:
tftp, tr, traceroute and so forth.

Would it perhaps be possible to add these into a standalone document, or two, ideally
a .md file, under doc/ or some such directory? This is just for curiousity; and also to
check on updates of toybox as more work is done here. At any rate, thank you for
reading this (it is also not strictly necessary as we can obtain the info via make menuconfig,
but I think a standalone text file may be easier to read online too; github provides a quite
convenient generic interface here).

[landley]

On 1/26/25 15:57, rubyFeedback wrote: Hey there, You provide a listing of entries that are currently not finished, aka: tftp, tr, traceroute and so forth.

Do you mean https://landley.net/toybox/status.html ?

Would it perhaps be possible to add these into a standalone document, or two, ideally a .md file, under doc/ or some such directory?

Are you suggesting I check in the generated file, or "be better about updating the documentation when you update the code"?

This is just for curiousity; and also to check on updates of toybox as more work is done here.

I only update status.html once per release. (After manually reviewing/updating roadmap.html, which isn't always as thorough as it should be because there's a lot to go through. It's in the release checklist www/release.txt which probably makes no sense to anybody other than me.) And since scripts/mkstatus.py was written in python and I haven't sat down to rewrite it in bash or something since python++ evicted python from most Linux distros, I've had to build the last release of python from source to run the generator.

At any rate, thank you for reading this (it is also not strictly necessary as we can obtain the info via make menuconfig, but I think a standalone text file may be easier to read online too; github provides a quite convenient generic interface here).

Define "generic". (Issue #128 is still open for a reason. I should cycle back to that...)