Hunt down changes with git log

[@masterofdizzzaster]

-p does actually stand for patch. Man page of git log says:
-p, -u, --patch
Generate patch (see section on generating patches).

[@diegodario1400]

hey thanks for sharing. I found that very useful for my daily work, keep on doing this tips man

[@mohamedeffat54]

thanks for the tips, I've been looking for ways to improve my git debugging skills to untangle hells of weirdness that happens on git and --follow seem like a pretty nice tool to use
any idea on how to figure out if a rebase had happened or better detect branch merges? i'd be a good video topic

[@tomontheinternet]

That would be a good topic. The next time I run into an issue like that I'll document what I learn and make a video.

[@stoicfloor]

awesome! Learned some new tricks! Could you tell me what the name of your command prompt customization is? It looks very pretty. Thanks in advance!

[@tomontheinternet]

Thanks!
I'm using starship.rs/

[@yusufaktepe]

Which diff tool are you using?

[@tomontheinternet]

I'm using Delta. github.com/dandavison/delta

[@AndyKoch]

git diff master --compact-summary
to get a summary of how the files were modified line adds or removals (+ and - notation)

[@tomontheinternet]

Going to check this out. Thanks