From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Luis Machado <luis.machado@arm.com>,
Nick Clifton <nickc@redhat.com>,
Carlos O'Donell <carlos@redhat.com>,
Binutils <binutils@sourceware.org>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: The GNU Toolchain Infrastructure Project
Date: Tue, 18 Oct 2022 14:45:39 -0400 [thread overview]
Message-ID: <20e6f3c3-60e4-cf67-e228-aec7293e7c2c@gotplt.org> (raw)
In-Reply-To: <d4b9d7cb-b86a-862b-1db2-de70d2f46d0e@arm.com>
On 2022-10-17 08:16, Luis Machado wrote:
>>> Binutils is tightly coupled to GDB though (or the other way around).
>>> I suppose both projects would
>>> need to seek agreement on this, otherwise they'd have to be split at
>>> some point.
>>
>> I couldn't see any follow-up discussion on the gdb mailing list. Have
>> there been discussions elsewhere and is there a direction y'all have
>> some consensus on?
>>
>> Sid
>
> There have been none to my knowledge. And no consensus either.
>
The FSF is hosting a call for this next week, so hopefully that'll help
the gdb community start a discussion and come to some consensus:
https://sourceware.org/pipermail/overseers/2022q4/018997.html
Sid
next prev parent reply other threads:[~2022-10-18 18:45 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b00dc0aa-31a6-a004-a430-099af3d0f6d1@redhat.com>
[not found] ` <558996ac-e4a0-cf77-48b9-f7d0e13862e8@redhat.com>
2022-10-17 11:48 ` Luis Machado
2022-10-17 12:08 ` Siddhesh Poyarekar
2022-10-17 12:16 ` Luis Machado
2022-10-18 18:45 ` Siddhesh Poyarekar [this message]
[not found] <d9cb6cf9-89f5-87bb-933b-a03240479e71@redhat.com>
[not found] ` <a9396df3-5699-46ef-0b33-6c7589274654@redhat.com>
2022-10-02 20:47 ` Mark Wielaard
2022-10-04 13:46 ` Siddhesh Poyarekar
2022-10-04 14:01 ` Frank Ch. Eigler
2022-10-04 14:13 ` Siddhesh Poyarekar
2022-10-04 14:19 ` Frank Ch. Eigler
2022-10-04 14:33 ` Siddhesh Poyarekar
2022-10-04 14:41 ` Frank Ch. Eigler
2022-10-04 14:55 ` Siddhesh Poyarekar
2022-10-04 15:07 ` Frank Ch. Eigler
2022-10-06 21:42 ` Alexandre Oliva
2022-10-04 17:10 ` Christopher Faylor
2022-10-04 17:17 ` Siddhesh Poyarekar
2022-10-04 18:42 ` Christopher Faylor
2022-10-04 19:05 ` Mark Wielaard
2022-10-04 19:10 ` Siddhesh Poyarekar
2022-10-06 20:02 ` Mark Wielaard
2022-10-06 20:12 ` Christopher Faylor
2022-10-06 21:37 ` Siddhesh Poyarekar
2022-10-07 13:39 ` Mark Wielaard
2022-10-06 21:07 ` Siddhesh Poyarekar
2022-10-06 21:36 ` Frank Ch. Eigler
2022-10-06 21:44 ` Siddhesh Poyarekar
2022-10-06 22:57 ` Frank Ch. Eigler
2022-10-11 13:02 ` Siddhesh Poyarekar
2022-10-07 8:57 ` Mark Wielaard
2022-10-11 13:24 ` Siddhesh Poyarekar
2022-10-11 14:23 ` Frank Ch. Eigler
2022-10-11 15:58 ` Alexandre Oliva
2022-10-11 17:14 ` David Edelsohn
2022-10-11 18:12 ` Frank Ch. Eigler
2022-10-12 8:00 ` Mark Wielaard
2022-10-12 13:18 ` Florian Weimer
2022-10-12 21:23 ` Mark Wielaard
2022-10-12 15:15 ` Jonathan Corbet
2022-10-12 10:55 ` Alexandre Oliva
2022-09-27 20:08 Carlos O'Donell
2022-09-28 22:38 ` Carlos O'Donell
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=20e6f3c3-60e4-cf67-e228-aec7293e7c2c@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=binutils@sourceware.org \
--cc=carlos@redhat.com \
--cc=gdb@sourceware.org \
--cc=luis.machado@arm.com \
--cc=nickc@redhat.com \
/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).