Re: [PATCH] sim: ChangeLog: move arch-specific entries into the arch dir

[Mike Frysinger via Gdb-patches <gdb-patches@sourceware.org>]

[-- Attachment #1: Type: text/plain, Size: 1862 bytes --]

On 11 Jan 2021 11:10, Andrew Burgess wrote:
> * Simon Marchi <simon.marchi@polymtl.ca> [2021-01-09 12:02:23 -0500]:
> > 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.
> 
> If sim/ was released as a separate project then sure, but while it's
> released as part of GDB I'd rather we just copied the policies of
> gdb/.

it has the structure to be released by itself already.  you can run
`./src-release.sh sim` and get a usuable release archive.  you can't
do that for just any toplevel dir.  this is because the project is
completely usable w/out gdb and always has been.

i don't think we've made sep releases for a very long time as people
have been fine reusing the gdb cycle: it's on a reasonable periodic
schedule, does all the release management/branching, sim changes have
often been slow, and the userbase for only the sim is small.

so i don't think saying "we have to make dedicated releases" just to
"prove" that we're independent from gdb is correct.
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]