[Top][All Lists]

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

Criteria for Acceptable Git to ChangeLog

From: John Darrington
Subject: Criteria for Acceptable Git to ChangeLog
Date: Sat, 12 May 2018 07:18:47 +0200
User-agent: Mutt/1.5.23 (2014-03-12)

The situation of this discussion seems to be as follows:

On one side we have a party who believes that ChangeLog files are of little
value and the effort required to maintain them is tedious.  They don't 
want to have to keep ChangeLogs in their repositories.

On the other side there are people who consider ChangeLog files to be
useful, but are willing to accept their absence if and only if they can
be reliably auto generated by a program or script.

So I don't think this discussion is going to move further unless we
start talking about the minimum acceptable criteria for a scm-to-change-log
program should be.

Does anyone have any suggestions about that?  


Avoid eavesdropping.  Send strong encrypted email.
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.

Attachment: signature.asc
Description: Digital signature

reply via email to

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