> We should not let GitHub take over the Git brand like they try to do with blog posts like this one.

Is there a similar blog post by the actual git team sharing this information? If so, let's link to that - but as I am not aware of one, I do appreciate github's git release announcements because they are typically a much easier way to learn about new git features than reading the entire release emails [0]

[0]: https://www.mail-archive.com/[email protected]/msg145986.h...

> Is there a similar blog post by the actual git team sharing this information?

Peff is a member of the Core Git team and is primarily working on open source git.

OK, we've changed the title to a representative phrase from the first paragraph.

> Most coders these days say they use git while in reality the have no clue how it works and how to use it.

I mean, that is true whether they're using GUIs on top of git or git's actual CLI.

> Most coders these days say they use git while in reality the have no clue how it works and how to use it

Come on, seriously? Where do you work?

I know right?! What kind of response is that?

I cant tell if this serious or sarcastic

I did see many who use git via say sourcetree, they do just click button to push and pull .. and they dont know much more

I dont think this is bad though

I would have an aneurysm if one of my coworkers or teammates didn’t know how to use git. The documentation is widely available, there are exactly zero excuses available.

Like a product manager? You think it's reasonable to understand all the nuances and capabilities of an obtuse CLI tool that manages concurrent history? What you probably mean is the simplified concepts of Git without the capabilities to alter the interaction effects. You come off as the typical condescending developer who secretly looks down on people with different interests and responsibilities because they don't understand YOUR JOB.

The original comment was referring to coders. It's not a lot to ask people who are working on code to know how to use basic git commands.

Dude that’s a total overreaction. I was referring to software engineers. Why would a product manager need to know how to use rebase or bisect?

I was going to say that just from the title, they're not really representing themselves as being git, but then in the body of the post, they actually use "us" to refer to git

> Git v2.16 adds a new fsmonitor hook that relies on the operating system to tell us what has changed. Doing so allows us to avoid the repeated stat()

arent't they using "us" to refer to "us, the programmer using git" as in "...to tell us, the user of git, what has changed"?