bug-standards
[Top][All Lists]
Advanced

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

Re: Using VC for change descriptions


From: John Darrington
Subject: Re: Using VC for change descriptions
Date: Mon, 27 Nov 2017 06:59:36 +0100
User-agent: Mutt/1.5.23 (2014-03-12)

On Sun, Nov 26, 2017 at 01:25:04PM -0800, Paul Eggert wrote:
     Richard Stallman wrote:
     >If we stop manually maintaining ChangeLog files because version
     >control systems provide information just as good, we should include
     >that information instead of the ChangeLog files.
     
     Yes, and that's a stated part of the proposal: projects must maintain a
     public repository. The repository should publish all the relevant
     version-control information, including commit messages, dates, and
     authors -- all the info that traditionally would appear in ChangeLog
     files.

There are a couple of scripts published (I think one of them is part of gnulib)
which automatically convert a git history, into a ChangeLog file.  If the 
commit messages have been composed thoughtfully,  I believe such ChangeLog files
are indistinguishable from manually maintained ones.   Several Gnu projects
are already creating ChangeLogs this way.

J'



-- 
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]