This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author cheryl.sabella
Recipients cheryl.sabella, terry.reedy
Date 2017-07-09.11:06:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
`git log` is the magic command.  I won't be able to do it justice because it has too many options, but here are a few.

`git log` shows all commit message history on the current branch.
`git log -p` (p for patch) shows the actual diffs
`git log -p -- path/to/file` shows the diffs for one file
`git log --grep` (with or without file) greps the commit messages
`git log -Sword` (with or without file) greps the file content for word

I don't know how gitgui integrates those commands.

Having said that, I also don't know how to look at branches, so because of the name change on the file, I looked at 3.3 in github and trudged through.  But, it was more of a divide and conquer, so it didn't take long.  I randomly opened a commit and checked the file for the line changes.  I'm sure there would have been a way to do it with git log.
Date User Action Args
2017-07-09 11:06:22cheryl.sabellasetrecipients: + cheryl.sabella, terry.reedy
2017-07-09 11:06:22cheryl.sabellasetmessageid: <>
2017-07-09 11:06:22cheryl.sabellalinkissue30868 messages
2017-07-09 11:06:21cheryl.sabellacreate