On Tue, Aug 22, 2017 at 9:34 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote: >> While this works, it feels sub-optimal. Is there a better / smarter way? > > I do not think so; you want three things to match and you have a way > to compare two things at a time. Right. I was just thinking if there's a lesser known command like "git diff --no-index", but instead of taking two paths, take just one path and a commit. > By the way, I think your second check should compare > > rev-parse HEAD^{tree} $that_commit^{tree} > > as you are checking if the tree exactly matches. In fact, I was considering to use "git diff HEAD $that_commit" as I don't really care whether the SHA1s are equal, but just about the file contents / tree. -- Sebastian Schuberth