Git a branch is a chain, commit every commit has its parent commit, a branch of the whole evolution process is all recorded in the form of chain, can use the Git log to check all commit.

Submitted from a certain point, the updated file a.t xt, and b.t xt, and then submit to commit 1, after again and then update b.t xt, to commit 2.

This time we use the git log command, we can see commt 1 and 2, commit because it is against the entire branch,
Use the git log a.t xt, can only see the commit 1, because there is no a.t commit 2 xt changes,

The problem is that for a certain files, such as a.t xt, Git system will also maintain a commit chain?

CodePudding user response:

Don't
Very simple, you back to a commit point, is for the branch back to back, not according to a single file back
For example, a.t xt, b.t xt did commit 1, b.t xt did commit 2, and then you changed a.t xt, but when you're trying to return the b.t xt commit 1 version, you can separate the fallback b.t xt? Can't back, so a.t xt will also be back to back, so, commit chain is not in a single file management,