This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Using the vcs_to_changelog.py script


> From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
> Cc: binutils@sourceware.org, gdb-patches@sourceware.org
> Date: Thu, 13 Feb 2020 20:09:21 +0100
> 
> On Thu, 2020-02-13 at 20:58 +0200, Eli Zaretskii wrote:
> > I have yet to see this accepted as GNU policy.  And at least
> > personally, having a ChangeLog in a tarball that just says which
> > function was changed on what date is almost useless to me (and I do
> > sometimes need to work without access to the VCS repositories).
> It looks easy to have a script to generate a file that contains all
> the git log messages + the diff for each commit
> in case detailed changes have to be analysed off-line, without a git repository.

How does this help when all you have is the release tarball?

Anyway, I really don't think we should re-iterate the many months of
discussions on gnu-prog-discuss, which led me to propose the change in
standards.texi.  Those discussions have beaten this horse to death,
and I don't think we will invent any new arguments for or against
producing ChangeLog files from VCS logs.  If we decide to produce
ChangeLog files at the time the release is tarred, then the ChangeLog
files should be informative and useful; otherwise it's tantamount to
deciding to drop ChangeLog's for the releases as well.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]