Re: Why 'git commit --amend' generates different HEAD sha1 each time when no content changes

On Dec 30, 2007 6:59 PM, Matthias Kestenholz [off-list ref] wrote:

On Sun, 2007-12-30 at 18:56 +0800, Ping Yin wrote:

quoted

AFAIK, commit sha1 is only determined by commit object content (say
parent commit, tree sha1 and so on). So why 'git commit --amend'
changes the commit sha1 when no content changes as following shows.

The full commit includes a timestamp too, which changed. Try setting the
GIT_AUTHOR_DATE and GIT_COMMITTER_DATE environment variables, you should
get the same SHA-1 everytime.

Thanks. With 'git show --pretty=fuller', I find that commit date
changes each time and that author date keeps the same.



-- 
Ping Yin