Pragmatic Guide to Git

31	Filtering the Log Output

Git’s log is useful way to track what the original developer—often yourself—was thinking when they made a change, but it often provides too much information. You can use git log’s many parameters to filter the results it displays, zeroing in on the information that’s important to you.

You can start to filter the results by providing Git with a directory or path. You specify the path as the last parameter. To be safe, separate the path from other parameters with -- (two dashes). Otherwise, Git can’t tell the difference between the branch or tag work and the path work.

You can also filter the log based on the time of the commit. Using the --since or --after parameter, you can look at commits after ...