From: Simon Marchi <simark@simark.ca>
To: Zander Work <zdw@google.com>, 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: Thu, 14 May 2026 10:23:18 -0400 [thread overview]
Message-ID: <64b04f80-6376-4f07-a677-702d32e73068@simark.ca> (raw)
In-Reply-To: <CAB3ousCOhEbPD9AfRkgLYzS7gT+GQ8co6jFUtoSENBOaU8OBew@mail.gmail.com>
On 2026-05-12 09:05, Zander Work wrote:
> 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
That is strange, because many of us (me included) contribute under a blanket assignment.
Unless it has been revoked for some reason, I also remember Google
having a blanket assigment for all GNU tools projects. I see an entry
for that in the copyright assignment file we have access to. Can you
ask the FSF clerk to confirm that?
Simon
next prev parent reply other threads:[~2026-05-14 14:23 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
2026-05-12 13:10 ` Eli Zaretskii
2026-05-14 14:23 ` Simon Marchi [this message]
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=64b04f80-6376-4f07-a677-702d32e73068@simark.ca \
--to=simark@simark.ca \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=guinevere@redhat.com \
--cc=tom@tromey.com \
--cc=zdw@google.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