On Sun, Jul 24, 2016 at 11:12:12AM -0700, Jon Forrest wrote: > > Those of us who write instructional material about Git all face the same problem. > This is that we can't write step by step instructions that show the results of > making a commit because users will always see different commit IDs. > This is fundamental to the design of Git. > > Even if the instructional material tells users to use standard author and committer > information, (e.g. john.doe@xxxxxxxxxxx) and shows the text of the file being committed > and the commit message to add, the resulting commit ID will differ from reader to reader > since the commit will presumably take place at different times. And what is the problem with that, if you are doing it with instructional purposes? Let's assume that this helps and not confuses later when the commits *do* change. What is the problem you face? I mean, for some examples you can use HEAD, HEAD^, HEAD~4, etc. and that always works, no matter the commit id. In which cases do you want/need the commit ids to be equal? Can you be more specific? Thanks a lot, Rodrigo -- 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