When is Linux going to rename “man” which according to my employer is a non-inclusive word and flagged in pull requests

[delayed]

I’m disappointed that this headline will lead to more clicks. This is your reminder that in git the branch name is just a pointer to a commit. Replacing that pointer with another pointer will cause some breakage, which may or may not be worth your time to fix. Good thing that git isn’t forcing this change on existing repos, just new ones that no automation depends on. In any case GitHub makes the renaming fairly seamless (https://github.com/github/renaming?tab=readme-ov-file#rename...).

The other git 3.0 changes are more consequential and worthy of discussion - changing from SHA-1 to SHA-256 for greater security and performance, changing the storage format for performance and introducing Rust.

Yet again the whining twitter-people get another win.