Re: Is it time to drop ChangeLogs?

[Dmitry Gutov]

On 03/08/2016 11:27 PM, David Caldwell wrote:

> > How would such commit indicate a relation to an existing commit?
>
> I was thinking something along the lines of "reword: <HASH>" in the message.

That would work.

> > How about putting all corrections as plain files in a subdirectory? Each
> > file will be named after a commit whose message it's "changing". IIRC,
> > I've seen such idea mentioned before, and it seems like it should work.
>
> Yeah, It would work as well. I just thought it would be nice to keep
> meta-data corrections in the meta-data itself.

I figured it would be nice to be able to quickly find it. In 
vc-print-log integration code, for example.

> I don't believe they do, by default. And if they need to be amended to
> include that, you might as well amend to include the fixed commit-log
> instead.

The do when produced like we recommend in admin/notes/git-workflow (with 
-x argument). If it doesn't, it's not the end of the world. Someone will 
just have to issue a correction for the new hash as well.