From: Luis Machado <luis.machado@linaro.org>
To: Simon Marchi <simon.marchi@polymtl.ca>,
Stephen Webb <swebb@blackberry.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Proposal to Removal of QNX Neutrino support from GDB
Date: Wed, 4 Aug 2021 16:47:31 -0300 [thread overview]
Message-ID: <3d26fb37-982a-3c97-a000-c76abd3660d6@linaro.org> (raw)
In-Reply-To: <b4bb0926-e5d7-522a-9a71-f16e6668ae43@polymtl.ca>
On 8/4/21 2:21 PM, Simon Marchi via Gdb wrote:
> On 2021-08-04 11:14 a.m., Stephen Webb wrote:
>> I am still wrestling with internal demons on this, I apologise for the
>> silence. I should have some basic binutils patches soon as a first step.
>
> No worries, as long as we get regular updates to know the project is not
> dead.
>
>> On that topic, are binutils changes handled the same as gdb changes or
>> are they a separate process? The history is very confusing.
>
> The process is roughly the same, only that the patches are sent to
> binutils@sourceware.org instead of gdb-patches@sourceware.org. Also,
> make sure your copyright assignment covers both projects (GDB and
> binutils).
>
> A small difference in process is that we don't use ChangeLog entries in
> GDB anymore, whereas binutils still uses them.
master binutils has abolished ChangeLogs as well.
https://sourceware.org/pipermail/binutils/2021-June/117016.html
Confirmed by H.J. here:
https://sourceware.org/pipermail/binutils/2021-August/117591.html
next prev parent reply other threads:[~2021-08-04 19:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 14:47 Simon Marchi
2020-12-11 17:31 ` Stephen Webb
2020-12-11 17:52 ` Simon Marchi
2021-02-25 21:16 ` Simon Marchi
2021-02-27 15:48 ` Stephen Webb
2021-02-28 15:28 ` Simon Marchi
2021-03-01 16:45 ` Simon Marchi
2021-08-04 14:51 ` Simon Marchi
2021-08-04 15:14 ` Stephen Webb
2021-08-04 17:21 ` Simon Marchi
2021-08-04 19:47 ` Luis Machado [this message]
2022-04-05 14:30 ` Simon Marchi
2023-03-28 19:24 ` 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=3d26fb37-982a-3c97-a000-c76abd3660d6@linaro.org \
--to=luis.machado@linaro.org \
--cc=gdb@sourceware.org \
--cc=simon.marchi@polymtl.ca \
--cc=swebb@blackberry.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).