On 09 Jan 2021 12:02, Simon Marchi via Gdb-patches wrote:
> On 2021-01-08 4:57 a.m., Andrew Burgess wrote:
> > * Tom Tromey <tom@tromey.com> [2021-01-07 13:57:14 -0700]:
> >> Mike> merging them into one causes extra pain due to conflicts.  having sep
> >> Mike> arch ones alleviates that a little as you don't normally have people
> >> Mike> working on the same arch at the same time.
> >>
> >> Mike> ideally we'd throw away these archaic ChangeLog files entirely.  they
> >> Mike> are a huge waste of time for everyone and would be much better served
> >> Mike> writing proper git commit messages.  it isn't the 80s/90s anymore.
> >>
> >> I'm +1 on that, but other maintainers like them, so we've been keeping
> >> them around.
> > 
> > For the record I see them as a waste of time too.
> 
> Well, I'm not a maintainer of the sim project, but the maintainers of
> the sim project could decide to not do ChangeLogs anymore.
> 
> See the section that talks about VCS:
> 
> https://www.gnu.org/prep/standards/html_node/Change-Logs.html

i was thinking "project" encompassed everything in the git tree rather
than the individual ones.  if it's defined more narrowly, then yes, lets
stop this pain in the sim/ tree.

i don't know what the gdb release process looks like, but it's def not
just `git archive`.  we should see if we can integrate gnulib's script
(gitlog-to-changelog) to generate the sim/ChangeLog in the tarballs.
-mike