From: Mike Frysinger <vapier@gentoo.org>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: binutils@sourceware.org, gdb@sourceware.org
Subject: Re: Maintenance of top-level files
Date: Wed, 8 Sep 2021 16:18:22 -0400 [thread overview]
Message-ID: <YTkajg7Jf1/8KkMt@vapier> (raw)
In-Reply-To: <20210908082349.GC1487362@embecosm.com>
[-- Attachment #1: Type: text/plain, Size: 1457 bytes --]
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-09-08 20:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 8:23 Andrew Burgess
2021-09-08 20:18 ` Mike Frysinger [this message]
2021-09-10 4:58 ` Alan Modra
2021-09-10 14:35 ` Simon Marchi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YTkajg7Jf1/8KkMt@vapier \
--to=vapier@gentoo.org \
--cc=andrew.burgess@embecosm.com \
--cc=binutils@sourceware.org \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).