On Tue, Oct 15, 2019 at 1:42 AM Ruediger Pluem <rpl...@apache.org> wrote: >...
> Would we lose this possibility [of editing log messages] with git? > Yes. The log message is part of the commit hash. You can effectively delete the "tip" commit of a line-of-development, and replace it with a new commit (ie. same code changes, but edited log msg). That new commit would have a different hash. If people sync'd the old commit/hash, their clones are basically broken post-edit. It is effectively impossible to edit a log message if it is not-tip. That is because each ongoing commit has a "parent [hash]" incorporated into its hash signature. So if you go back in time to edit C1, then you're gonna to regenerate hashes for C2, C3, and C4 that came after it. With the corresponding breakage of clones. Arguments can be made for whether this is pro/con, but I think is not worth discussing here. HTH, -g
