From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org, binutils@sourceware.org
Cc: Dhruv Chawla <dhruvc@nvidia.com>
Subject: Re: [PATCH] libiberty: sync with gcc commit df3510f80e7c02d9
Date: Tue, 09 Jun 2026 12:13:10 +0100 [thread overview]
Message-ID: <87a4t4q855.fsf@redhat.com> (raw)
In-Reply-To: <ff87d7cb74f9d3d3b81aeca0a979d3dcc1531567.1781002240.git.aburgess@redhat.com>
Andrew Burgess <aburgess@redhat.com> writes:
> From: Dhruv Chawla <dhruvc@nvidia.com>
Apologies Dhruv, due to how I pulled the patches from gcc to
binutils-gdb, you ended up as the author in my local branch, which I
failed to spot prior to sending the email out.
I've updated the author to myself now, so this back-port will not be
blamed on you :)
Thanks,
Andrew
next prev parent reply other threads:[~2026-06-09 11:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 10:52 Andrew Burgess
2026-06-09 11:13 ` Andrew Burgess [this message]
2026-06-20 12:54 ` Andrew Burgess
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=87a4t4q855.fsf@redhat.com \
--to=aburgess@redhat.com \
--cc=binutils@sourceware.org \
--cc=dhruvc@nvidia.com \
--cc=gdb-patches@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