5 ms·
The more public and more developers it has, the more I use it. The project where I use it the most is Linux kernel. It's also probably because there's a strong
by megous 7y ago
The more public and more developers it has, the more I use it. The project where I use it the most is Linux kernel. It's also probably because there's a strong requirement to actually write useful commit descirptions. But if changes come from so many developers, it's very useful to catch up on news, what's coming to the next kernel release, what changed in what driver or subsystem, what might have caused the regression I'm seeing, who to contact, etc.
On personal projects I don't use it that much.
- leppr 7y agoYea, the only times where I don't use it is when I'm working solo on small projects. Then the dirty tricks like duplicating files into `.bak` or `-ver3`, comment-out unused code for potential reuse later, etc, are actually more time-efficient at least for a non-git wizard like me. It's invaluable in larger projects, even as small as 2 persons.
- megous 7y agoI mean, I still use version control for pretty much everything. I just don't look at history all that much or try to write very careful commit messages for the small personal projects.