On Tue, Mar 12, 2013 at 05:12:28PM -0600, Matt McClure wrote: > On Mar 12, 2013, at 1:25 PM, John Keeping <[email protected]> wrote: > > > When I tried this I got the expected behaviour even without this patch. > > git diff --raw commit > > emits the null SHA1 if the working tree file's stat differs from the > blob corresponding to commit. Is that the case you observed?
Yes, although it's slightly more subtle than that - the null SHA1 only occurs if the working tree file has unstaged changes; if you add the changes to the index then the null SHA1 is no longer used since the blob is now available in Git's object store. John -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
