"Record changes" insists on recording the _delta_ between the parent commit and the new revision, which can be mis-leading, since Git is really snapshot-oriented. The new wording may be less misleading. --- I'm actually resurecting a new thread : http://thread.gmane.org/gmane.comp.version-control.git/68647/focus=68823 where a user was not understanding why custom diff drivers were not used by "commit" to tell whether the tree had changed ("I keep doing git diff's and it says there is no difference, but then git commit keeps telling me there is"). Documentation/git-commit.txt | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/Documentation/git-commit.txt b/Documentation/git-commit.txt index b5d81be..c7f728f 100644 --- a/Documentation/git-commit.txt +++ b/Documentation/git-commit.txt @@ -3,7 +3,7 @@ git-commit(1) NAME ---- -git-commit - Record changes to the repository +git-commit - Record a new revision in the repository SYNOPSIS -------- -- 1.6.2.2.449.g92961.dirty -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html