From: Sam James <sam@gentoo.org>
To: Simon Marchi <simark@simark.ca>
Cc: gdb@sourceware.org
Subject: Re: Updating libbacktrace
Date: Mon, 11 Mar 2024 17:03:39 +0000 [thread overview]
Message-ID: <87h6hcog44.fsf@gentoo.org> (raw)
In-Reply-To: <7bf4f993-11d6-4b5c-a70b-cbbe00399952@simark.ca> (Simon Marchi's message of "Mon, 11 Mar 2024 11:30:16 -0400")
Simon Marchi <simark@simark.ca> writes:
> On 3/8/24 12:28, Sam James via Gdb wrote:
>> Hi all,
>>
>> Could one of the GDB global maintainers possibly update libbacktrace
>> from the copy in gcc.git?
>>
>> I'm also happy to do it if delegated to. Whatever works for me.
>>
>> I originally asked at https://sourceware.org/PR31327 (as it fixes some
>> test failures) where Ian ACKed it, but wasn't sure of the policy on
>> it. Nick, the binutils maintainer, deferred to GDB as GDB is the primary
>> consumer of libbacktrace.
>>
>> Nick also suggested we clarify its status in MAINTAINERS.
>>
>> thanks,
>> sam
>
> Hi Sam,
Hi Simon,
>
> The easiest would be if you sent a patch to gdb-patches (and maybe CC
> binutils) for it.
Will do. Sorry, I should've just done that, probably.
>
> Thanks,
>
> Simon
thanks,
sam
prev parent reply other threads:[~2024-03-11 17:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 17:28 Sam James
2024-03-11 15:30 ` Simon Marchi
2024-03-11 17:03 ` Sam James [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=87h6hcog44.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=gdb@sourceware.org \
--cc=simark@simark.ca \
/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).