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

From: Ping Yin <pkufranky@gmail.com>
Date: Dec 30, 2007, 11:19 UTC
Message-ID: <46dff0320712300319s72dfc865oc71463cfe4e20cd0@mail.gmail.com>
In-Reply-To: <1199012360.15996.6.camel@futex>

On Dec 30, 2007 6:59 PM, Matthias Kestenholz <mk@spinlock.ch> wrote:

Show 11 quoted lines

>
> On Sun, 2007-12-30 at 18:56 +0800, Ping Yin wrote:
> > 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.
>

-- 
Ping Yin