There is a great need for an additional fork of the dcamp project. We need this in Q3.
Yeah, I think that some would prefer this task to be completed as soon as possible.
I think a few attached screenshots of the running process would be reasonable test coverage.
I'm not sure dcamp should be assigned this bug. Does his wife have a bugzilla account? He did ALMOST NOTHING.:)
We need this bug fixed on all platforms and architectures. :)
would like a UX review on this before it's marked resolved. I hear there's a work in progress patch that I'd like to get attached here.
(In reply to comment #3)
> I'm not sure dcamp should be assigned this bug. Does his wife have a
> bugzilla account? He did ALMOST NOTHING.:)
We should at least get Mrs Camp to review this. Maybe even request superreview from the grandparents.
I believe that hot curries help ... there are a few things that can fix this quickly.
Created attachment 551522 [details]
pushed (with great effort) to the live branch.
well done, sir! Verified in today's video meeting.
Comment on attachment 551522 [details]
I betcha this child process has already figured out how to communicate properly with the parent process. Once the sleep() call is done, he'll send a signal for sure.
Good work, he looks like he will be a metal drummer for sure