Here is what email patches are all about:

https://blog.ffwll.ch/2017/08/github-why-cant-host-the-kerne...

I tried email patches with another person myself. The only reason GH won here, is because the git people made one fatal mistake: They forgot to include the tree hash and only show the commit hash in the email patch. But the commit hash is useless. When you email patch, then commits people want to treat as "the same" and talk about have different hashes. The commit times differ and there is not only the commit author, but also the committer.

We stopped doing email patches, because commit hashes became useless for communicating with each other.

GitHub made commit hashes "constant" in a way people care about.

For our purposes, tree hashes would have been much better in practice.

The git user interface is literally "git porcelain". It cuts you for no reason.

That's not the only problem with git send-email by a long way. Even the setup process is extremely painful.

Does -Ofast still ignore -fno-fast-math ?

Have had to do this live in a production MtG card management application. It worked well. The owner kept their MtG card money. Lisp saved the day.

Unix and POSIX are fractally a booby trap.

Alpine Linux has a better shot at acceptable compile times.

Some FOSS software seems to maximize kernel IO last time I had a Gentoo.

> well behaved readers.

Around and around we go.

GNU coreutils is known for adding command libe options.

One of the big philosophical differences to the BSD's.

For a human being, it sucks both ways.

Welcome to building something new.

New things can be made optional and tested outside production, and should not be rolled out in an LTS edition.

>> should not be rolled out in an LTS edition.

The Rust coreutils were first rolled out in the previous release which was not LTS:

https://canonical.com/blog/canonical-releases-ubuntu-25-10-q...

That was for 6 months only and in an intermediate version that many don't update to, especially in production environments.

Isn't this how Kernighan and late Ritchie (K&R) ended up with unix and C?

Honestly, brilliant guys.

When C got its own standards committee they even rejected Ritchie's proposal to add fat pointers to C before it was too late to add them. Instead, we got the C abstract machine.

Filesystem access is mostly treated by users as serialized ACID transactions on "files in directories."

"Managing this resource centrally" is where unix syscalls came from. An OS kernel can be used like a specialized library for ACID transactions on hardware singletons.

People then got fancy with virtual memory, interrupts, signals, time-slicing, re-entrancy, thread-safety, and injectivity.

It doesn’t matter, whether you call the "kernel library" from C, C++, Fortan, BASIC, Golang, bash, Rust, etc.