Angelo Borsotti <angelo.borsotti <at> gmail.com> writes: > take a git commit without --allow-empty: if the trees are equal, it > creates no commit, > and if the trees are different it creates one. > Take then a git commit --allow-empty: if the trees are equal it may > create a commit or > not depending on the parent, message, author and date; if the trees > are different it > creates a commit. > So, the statement does not apply to commits in general. It does (as already shown to you). The ID of a commit object depends on the author, the time, the tree, and the commit message (did I forget something?). If all these are equal, no new physical object will be created. Independent of this: If you are on a branch "foo" pointing to a commit A and successfully do a commit (with --allow-empty or not), "foo" will afterwards point to a commit B different from A. So, a successful "git commit (--allow-empty)" will always add a commit to the branch you are on. -- Lars. -- 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