4 ms·
Then use `git log --oneline` and you don't have to see the lengthy details, until the inevitable day when you find you need them.
by JeffRosenberg 7y ago
Then use `git log --oneline` and you don't have to see the lengthy details, until the inevitable day when you find you need them.
- AlexCoventry 7y agoHow do you surface them when you need them, though? git grep?
- esotericn 7y agoSure? Or 'git log', then use the pager to search, or pipe into something with better fuzzy search, etc?
- JeffRosenberg 7y agoGit greps work if you're trying to search all the logs. I would think this detailed documentation would be most important when you're trying to understand a specific file or line of code. In that case, it's: - git blame (who wrote this?) - git show (look at the commit surfaced by blame)