Hell yes, I use it daily. I'm in AAA gamedev and the codebase I deal with goes back 20+ years. The last 10 years are readily accessible in Perforce and the rest can be found in another version control system. I am forever grateful to past engineers for outlining WHY they made their changes, and not WHAT the changes were per se. With thousands of engineers that have come and gone, this is incredibly useful information…
Ask HN: Do you ever truly use your revision history?
161–170 of 287 posts
Re: Ask HN: Do you ever truly use your revision history?
#162The 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 regressi…
It's invaluable in larger projects, even as small as 2 persons.
Re: Ask HN: Do you ever truly use your revision history?
#163Being able to pop into our SVN history made this a trivial issue ask.
Re: Ask HN: Do you ever truly use your revision history?
#164Earlier quoted context omitted.
This is good. I'm stealing it. It's using git as sort of a super-brain, helping you remember stuff you wouldn't otherwise. It's how I use gmail. Instead of shooting for inbox zero, I just leave anything in there that I might want to remember later and delete the rest. Then, many times years later, I can search through looking for important correspondence. Both of these stories are good examples of how simple but flex…
I use gmail the same way. I do feel that the search functionality could be improved though which I find ironic.
Re: Ask HN: Do you ever truly use your revision history?
#165Hell yes, I use it daily. I'm in AAA gamedev and the codebase I deal with goes back 20+ years. The last 10 years are readily accessible in Perforce and the rest can be found in another version control system. I am forever grateful to past engineers for outlining WHY they made their changes, and not WHAT the changes were per se. With thousands of engineers that have come and gone, this is incredibly useful information…
But that sounds like you value documentation, not necessarily the code history
Re: Ask HN: Do you ever truly use your revision history?
#166Re: Ask HN: Do you ever truly use your revision history?
#167Re: Ask HN: Do you ever truly use your revision history?
#168There were other core systems that I also read sometimes that were older, and it was extremely useful to understand their construction and function.
Re: Ask HN: Do you ever truly use your revision history?
#169Earlier quoted context omitted.
But that sounds like you value documentation, not necessarily the code history
Code history is documentation. There are lots of different kinds of documentation: code API level, module level, system level, tutorials, even books in some cases. Revision history is just another one of those levels, and I believe it is the best at capturing the "why"s of systems rather than just the "what"s.
Re: Ask HN: Do you ever truly use your revision history?
#170I use git blame and history at least once a week when bug sleuthing, and value it very highly.