From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: Alan Modra <amodra@gmail.com>
Cc: Tom de Vries <tdevries@suse.de>,
gdb-patches@sourceware.org, binutils@sourceware.org,
gcc@gcc.gnu.org
Subject: Re: [PING][PATCH] binutils-gdb/git: Handle *.ac and *.m4 files in .gitattributes
Date: Tue, 30 Dec 2025 22:54:34 +0000 (GMT) [thread overview]
Message-ID: <alpine.DEB.2.21.2512302247590.14570@angie.orcam.me.uk> (raw)
In-Reply-To: <aUNIUSsymi4uxjxJ@squeak.grove.modra.org>
[+cc GCC]
On Thu, 18 Dec 2025, Alan Modra wrote:
> I'll rubber-stamp this for the binutils side, but IMO there is no need
> for a global gdb maintainer to wait for approval from binutils
> maintainers for this shared file.
Should this be documented in top-level MAINTAINERS? Should this file be
kept in sync with GCC?
Maciej
prev parent reply other threads:[~2025-12-30 22:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 8:51 [PATCH] " Tom de Vries
2025-12-04 16:32 ` Tom Tromey
2025-12-17 21:25 ` [PING][PATCH] " Tom de Vries
2025-12-18 0:18 ` Alan Modra
2025-12-30 22:54 ` Maciej W. Rozycki [this message]
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=alpine.DEB.2.21.2512302247590.14570@angie.orcam.me.uk \
--to=macro@orcam.me.uk \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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