From: Sam James <sam@gentoo.org>
To: gdb@sourceware.org
Subject: Updating libbacktrace
Date: Fri, 08 Mar 2024 17:28:49 +0000 [thread overview]
Message-ID: <87plw4r5ta.fsf@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 496 bytes --]
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 377 bytes --]
next reply other threads:[~2024-03-08 17:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 17:28 Sam James [this message]
2024-03-11 15:30 ` Simon Marchi
2024-03-11 17:03 ` Sam James
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=87plw4r5ta.fsf@gentoo.org \
--to=sam@gentoo.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).