[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Is it time to drop ChangeLogs?

From: Dmitry Gutov
Subject: Re: Is it time to drop ChangeLogs?
Date: Tue, 8 Mar 2016 23:37:53 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.0

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

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.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]