Keywords: Git | file history | version comparison | git log | git diff
Abstract: This article provides a comprehensive overview of methods for viewing file modification history in Git, with detailed explanations of git log and git diff commands. Through practical examples, it demonstrates how to examine commit records for specific files, compare differences between versions, and contrasts command-line tools with graphical interfaces. The guide also addresses adaptation from Subversion to Git for history tracking, aiding developers in efficient code change management.
Fundamentals of Git File History
For developers transitioning from Subversion to Git, viewing file history is a common requirement. While Subversion users often rely on graphical tools like TortoiseSVN, Git offers more powerful command-line utilities for the same purpose.
Core Command: git log
The git log command is the primary tool for examining commit history. Each Git commit has a unique hash identifier, such as 14b8d0982044b0c49f7a855e396206ee65c0e787. To view the history of a specific file, use:
git log path/to/fileThis displays all commits that modified the file, including committer, date, and commit message.
Difference Comparison: git diff
To compare differences between two versions of a file, use the git diff command. Git uses the first few characters of commit hashes to identify versions:
git diff 14b8..b410 path/to/fileThis command shows all changes to the specified file between commits 14b8 and b410.
Detailed History Examination
For viewing specific modifications in each commit, use the -p option:
git log -p path/to/fileThis displays complete diff information for each commit, similar to the functionality of git whatchanged -p.
Graphical Tool Alternatives
For users preferring graphical interfaces, Git provides the gitk tool:
gitk path/to/fileThis opens a graphical interface specifically showing the modification history of the specified file, making it easier to track particular changes.
Comparison with Version Control Systems
As noted in reference articles, file history viewing in platforms like GitLab differs from BitBucket. GitLab displays complete commit history, while BitBucket offers a dedicated dropdown for single-file change history. This distinction reflects Git's distributed version control philosophy.
Practical Tips and Best Practices
In actual development, combining these commands enables efficient file change tracking. For instance, use git log to locate relevant commits, then employ git diff for detailed comparisons. For complex change histories, graphical tools like gitk or SourceTree provide better visualization.