Re: sim: replacing ChangeLog files with online git logs

[Eli Zaretskii <eliz@gnu.org>]

> Cc: gdb@sourceware.org
> From: Simon Marchi <simon.marchi@polymtl.ca>
> Date: Wed, 17 Mar 2021 11:52:49 -0400
> 
> In the GDB project, we write what I believe are excellent git commit
> messages that go in depth describing the observed problem and the
> solution provided by the patch.  That provides valuable information for
> anyone wanting to understand why the code is the way it is.  A list of
> modified symbols doesn't help.  So I am completely fine if the "list of
> modified symbols" part of the information is lost.

Well, if that's what the majority here wants, then so be it.

(The importance of having the list of modified symbols in the log is
that then one doesn't need advanced Git commands to find out which
changes modified a given function and why.)

> > If that is not an option that this community wants to adopt, then
> > gitlog-to-changelog is probably not the adequate solution, and we
> > should try using vcs-to-changelog.py (also in Gnulib).
> 
> I tried vcs-to-changelog, it gave horrible/useless results with our
> codebase.  This is not an option.

Too bad.  Maybe we should report this to the developer of the script,
it could help fix those shortcomings in the future.