> and partially because after all this time they still haven't taken an hour to deeply learn it.
I've spent a fair amount of time working directly with the object database, working with the latest Git features, filing bugs to upstream, working on my own source control extensions, working on successor version control systems (Jujutsu), attending and presenting at Git meetups... It's difficult to be more of a Git power user without being on the core developer team itself.
> If you don't have the same mental model and don't want to use those workflows
The workflows in question support the Linux mailing list patch workflow, which are described in `gitworkflows`, and are indeed what Git was originally created for.
Is it possible that maybe you haven't gotten a good feel for the model?
I've spent a fair amount of time working directly with the object database, working with the latest Git features, filing bugs to upstream, working on my own source control extensions, working on successor version control systems (Jujutsu), attending and presenting at Git meetups... It's difficult to be more of a Git power user without being on the core developer team itself.
> If you don't have the same mental model and don't want to use those workflows
The workflows in question support the Linux mailing list patch workflow, which are described in `gitworkflows`, and are indeed what Git was originally created for.
Is it possible that maybe you haven't gotten a good feel for the model?