Maintenance of top-level files

[Mike Frysinger]

On 08 Sep 2021 09:23, Andrew Burgess wrote:
> I wonder what the policy is these days regarding how the top level
> files are maintained, e.g. Makefile.def and configure.ac?
> 
> I know once upon a time these files were maintained in the gcc
> repository and then back-ported periodically to binutils-gdb, however,
> as far as I can see the last attempt to sync from gcc was this commit:
> 
>   commit f948b2de97884bfb4e5fc11d40a6bea9e0b096ae
>   Date:   Wed May 29 12:43:42 2019 +0100
> 
>       Sync top level files with versions from gcc.
> 
> Which was over 2 years ago.  This commit was then quickly reverted:
> 
>   commit e3f56a99f66298bb505d0426950b9716a853a5df
>   Date:   Thu May 30 11:17:19 2019 +0100
> 
>       Revert "Sync top level files with versions from gcc."
> 
> Since then there's been 30+ patches to the top level files.
> 
> My question then, is what are peoples thoughts on how these files
> should be managed?  Are we going to try and get back in step with gcc?
> Or are we happy to continue to diverging?

afaik, it's still "gcc first".  when i commit changes to the top-level files,
it's the same git commit (using `git am`), not a blank "sync files".  i think
a bunch of the other ones are the same way.

https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=17af39e1c0e590f4cb13d672c9ee850e871164ab
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=9cc11ab5bf10c6f7494f6015769cf81b6988317f
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://sourceware.org/pipermail/gdb/attachments/20210908/276859ac/attachment.sig>