I’m gonna be real with you, I don’t know who or what that is and I deliberately chose to ignore the likely sarcasm, but feel free to enlighten me.

Like I agree it is a better message in the edit, but I fear a lot of people are not ready to hear that yet and still need to work through the original before coming around to this… Still stuck in denial and whatnot.

So… “man doesn’t exploit man”? Sounds good!

Tortoisegit is God awful, stuck in 1999.

If it works don’t fix it. Not that it’s my go-to.

you just indicated you enjoy reading man pages

I have indicated that I do it, not that I enjoy it. But yeah, I prefer it to skimming 20 verbose blog posts and outdated Stackoverflow questions to find one that is actually related to my specific use case. And often enough the search results will be online versions of the man pages anyway. Not quite sure why you are so hostile about it, I just said “read the docs” basically.

A ton, like the ones integrated in many editors/IDEs, GitHub Desktop, the one with the little turtle icon, forgot its name… Using gitk all the time. Don’t get me wrong I have nothing against a GUI, just saying I had a much better learning experience with git once I started using the CLI and man pages instead of a GUI and random tutorials for them. It’s just a lot more accessible and better documented in my experience.

Just my 2¢ but disagree on this one. Where GUIs are usually powerful but inflexible, the CLI is both powerful and flexible. And getting into trouble usually means you have a print on the console that tells you exactly what happened and what concept or command to look up.

Matter of opinion and goals I guess, but if you want to understand git as a tool I recommend learning the CLI.

Read the policies yourself

I suggest reading this diff to the FAQs instead, paints a much clearer picture:

https://github.com/mozilla/bedrock/commit/d459addab846d8144b61939b7f4310eb80c5470e

Basically removes all the language about not selling data and some about privacy. Down in the comments someone argues this is due to a narrow legal definition of that language in certain jurisdictions, but that couldn’t sound more like an empty excuse if they tried. Actually all the reactions from Mozilla I have seen on this so far sound like pure corpo PR bullshit to me.