Re: Workflow to accumulate individual changes?

[Teemu Likonen]

On 2010-01-01 14:18 (-0500), Karl Fogel wrote:

> IIUC, in git the commit message is *not* part of the change's
> identity, it's just attached to the change, so you can edit the
> message later.

That's wrong--or your "change's identity" means something I don't
understand. In Git commit's author, committer, date, parent commits'
SHA1s, referenced tree object's SHA1 and commit message together make
the content of a commit object. From this content is calculated the SHA1
of that commit object. If you change any of these the SHA1 of the commit
object will be different and hence the whole commit object will be
different (i.e. its identity is different).

So no, it's not possible to change commit message (or any information
the commit object contains) without making it a different commit.


There is a related feature, though. New Git versions have "git notes"
command which allows user to add additional notes to commits. Such extra
notes can be added and removed freely and "git log" prints them after
the commit message. Notes can be sent between repositories but currently
it doesn't happen automatically with usual pull/push commands.

http://www.kernel.org/pub/software/scm/git/docs/git-notes.html