From: Luis Machado <luis.machado@arm.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Yvan Roux <yvan.roux@foss.st.com>,
pedro@palves.net, tom@tromey.com, gdb-patches@sourceware.org
Subject: Re: [PATCH v5] gdb/arm: Handle lazy FPU state preservation
Date: Mon, 10 Oct 2022 17:58:05 +0100 [thread overview]
Message-ID: <801e7ebb-96c9-368a-353b-8464ed33984d@arm.com> (raw)
In-Reply-To: <Y0RMzp6/orcETSDl@adacore.com>
On 10/10/22 17:48, Joel Brobecker wrote:
>> Speaking of which, I find the copyright verification to be a bit of a
>> nuisance. Every once in a while I need to verify a contributor's
>> copyright assignment, but I can't do it in an easy way. I usually ask
>> Mark W. to help me with it, which is something I could've done on my
>> own.
>
> Because having a copyright assignment on file is a condition for getting
> Write After Approval privileges, I only do the check when I notice
> that someone doesn't have an account (usually when the contributor
> says he cannot push the patch when I approve it). It's sufficiently
> rare that I haven't seen this as a big issue.
>
> I don't know if we can give access to the file to more people or not...
>
Sure, but I don't think we need access to the file itself, but it would certainly
help if we could verify someone is good to go given an e-mail or name I guess.
prev parent reply other threads:[~2022-10-10 16:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 8:48 Torbjörn SVENSSON
2022-10-05 14:28 ` Luis Machado
2022-10-09 23:45 ` Joel Brobecker
2022-10-10 7:20 ` Yvan Roux
2022-10-10 9:26 ` Luis Machado
2022-10-10 13:02 ` Pedro Alves
2022-10-10 13:06 ` Luis Machado
2022-10-10 14:50 ` Joel Brobecker
2022-10-10 16:35 ` Luis Machado
2022-10-10 16:48 ` Joel Brobecker
2022-10-10 16:58 ` Luis Machado [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=801e7ebb-96c9-368a-353b-8464ed33984d@arm.com \
--to=luis.machado@arm.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
--cc=tom@tromey.com \
--cc=yvan.roux@foss.st.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).