From: Zander Work <zdw@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org, guinevere@redhat.com, tom@tromey.com
Subject: Re: [PATCH v2] Use "output-radix" setting to format function offsets
Date: Tue, 12 May 2026 06:05:21 -0700 [thread overview]
Message-ID: <CAB3ousCOhEbPD9AfRkgLYzS7gT+GQ8co6jFUtoSENBOaU8OBew@mail.gmail.com> (raw)
In-Reply-To: <86zf24zwta.fsf@gnu.org>
On Tue, May 12, 2026 at 4:33 AM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > From: Zander Work <zdw@google.com>
> > Cc: guinevere@redhat.com,
> > tom@tromey.com,
> > Zander Work <zdw@google.com>
> > Date: Mon, 11 May 2026 18:32:38 -0700
> >
> > Thank you for the review Guinevere! I fixed the formatting issue you
> > flagged, and added your review tag.
> >
> > Global maintainers: I haven't done a FSF copyright assignment, please
> > let me know how I should do that.
>
> If you are an employee of Google, I think they have a blanket
> assignment covering all of their employees? Tom, am I right?
Our internal documentation says that Google has a CLA on file with
FSF, but the red warning on the Contributor Guide section 6 [1] makes
me think that isn't sufficient
[1] https://sourceware.org/gdb/wiki/ContributionChecklist#FSF_copyright_Assignment
>
> Failing that, we can send you the form to fill and the instructions to
> go with it, so you could start your assignment paperwork rolling.
>
> > This is a patch for a discussion [1] I had previously where it was
> > determined that it was a bug for GDB to not use the "output-radix"
> > setting for function offsets.
> >
> > This patch includes updates to the radix.exp tests, and I verified that
> > there were no new breakages added when running the full gdb testsuite
> > with this patch.
> >
> > I didn't make any changes to NEWS or a /gdb/ Changelog entry for this,
> > if I should please let me know.
>
> Yes, this needs an entry in NEWS. I think the descriptions of
> output-radix and of the "disassemble" command in the GDB manual should
> also be updated to reflect the change.
Sure thing, will update this patch with that later today.
>
> Thanks.
next prev parent reply other threads:[~2026-05-12 13:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-09 4:45 Zander Work
2026-05-11 14:14 ` Guinevere Larsen
2026-05-12 1:32 ` Zander Work
2026-05-12 11:33 ` Eli Zaretskii
2026-05-12 13:05 ` Zander Work [this message]
2026-05-12 13:10 ` Eli Zaretskii
2026-05-14 14:23 ` Simon Marchi
2026-05-14 15:15 ` Zander Work
2026-05-13 16:38 ` Tom Tromey
2026-05-13 16:50 ` Zander Work
2026-05-13 16:37 ` Tom Tromey
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=CAB3ousCOhEbPD9AfRkgLYzS7gT+GQ8co6jFUtoSENBOaU8OBew@mail.gmail.com \
--to=zdw@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=guinevere@redhat.com \
--cc=tom@tromey.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