Johannes Sixt <j.sixt@xxxxxxxxxxxxx> writes: > Note that git commit -m A --allow-empty *DID* create a commit. Only, that > it received the same name (SHA1) as the commit you created before it > because it had the exact same contents (files, parents, author, committer, > and timestamps). Obviously, your script was executed sufficiently fast > that the two commits happend in the same second. Correct. And this does not have anything to do with --allow-empty. You can "reset --soft HEAD^" immediately after committing a change and redo it to get the same effect. If you commit the same state with the same history with the same message as the same person at the same time, you will reliably get the same commit object. And that is fundamental property called reproducibility. There is nothing to be alarmed by this exercise. -- 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