sim: replacing ChangeLog files with online git logs
Eli Zaretskii
eliz@gnu.org
Wed Mar 24 17:39:24 GMT 2021
> Date: Wed, 24 Mar 2021 16:59:18 +0000
> From: Andrew Burgess <andrew.burgess@embecosm.com>
> Cc: Mike Frysinger <vapier@gentoo.org>, gdb@sourceware.org
>
> * Eli Zaretskii <eliz@gnu.org> [2021-03-24 18:46:38 +0200]:
>
> > > Date: Tue, 23 Mar 2021 23:45:24 -0400
> > > From: Mike Frysinger <vapier@gentoo.org>
> > > Cc: gdb@sourceware.org, Andrew Burgess <andrew.burgess@embecosm.com>
> > >
> > > Eli: those patches look OK to you too ?
> >
> > They just add the script to our repository, AFAICT, so I of course
> > have no objections.
>
> No the second proposes to replace the current ChangeLog with one
> auto-generated upon release.
>
> This ChangeLog would in effect be a reformatted `git log` output.
I don't object to that, either. The question is: what we will require
the Git log messages to contain then? Currently, the entire ChangeLog
entry goes there, but once the manually written ChangeLog files are
retired, what will remain? That was the crux of the recent
discussion.
> For the simulator this would mean there would no longer be any file
> that contained output in the format as:
>
> * file.c (symbol): description.
Well, I personally will lament the loss of that information. It's up
toy you-all to decide how much does that weigh.
More information about the Gdb
mailing list