News for hackers. Stuff that matters.

A comment on My Favourite Git Commit. Parent comment

Re:My Favourite Git Commit by JeffRosenberg on Friday October 18, 2019 @08:30AM (#21290782)
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.
[ Parent | on HN ]
Re:My Favourite Git Commit by AlexCoventry on Friday October 18, 2019 @10:32AM (#21291691)
How do you surface them when you need them, though? git grep?
[ Parent | on HN ]
Re:My Favourite Git Commit by JeffRosenberg on Friday October 18, 2019 @01:29PM (#21293308)
Git 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)

[ Parent | on HN ]
Re:My Favourite Git Commit by esotericn on Friday October 18, 2019 @12:26PM (#21292711)
Sure? Or 'git log', then use the pager to search, or pipe into something with better fuzzy search, etc?
[ Parent | on HN ]