3 ms·
There are definitely warts and sharp corners. Inconsistent cli api. The story for binaries with Git-LFS is still a mess (try using git over SSH with LFS or expl
by alkonaut 5y ago
There are definitely warts and sharp corners. Inconsistent cli api. The story for binaries with Git-LFS is still a mess (try using git over SSH with LFS or explain to a newcomer why it doesn’t work). Conflict resolution is still half stupid with very few easy ways of adding better more specialized merge drivers and deploying it over a company. Improvements like ReReRe and similar aren’t well integrated and enabled by default. Instead they are obscure additions so that you can get a less infuriating behavior. But only if you press the right buttons first.
The worst aspect of it though is you can’t set it up to be properly centralized so that you truly bless a location which can keep things like branch name policies, distribute hooks to all employees etc. All that has to be built (poorly) on top, with ample opportunity to accidentally sidestep.
- zibzab 5y agoTechnically, LFS isn't part of git and was added by a third party to solve a problem they had.
- alkonaut 5y agoYes. And it shows up as a massive hole in the feature set of git. Had it been a first class citizen together with other centralized workflow features, then obviously lfs would have worked over ssh. git is that it’s a tool written to solve distributed version control for Linux which is nearly the only project that’s effectively using distributed version control. Everyone else uses git for centralized version control. And it’a not a perfect fit.