From: Pedro Alves <pedro@palves.net>
To: Luis Machado <luis.machado@arm.com>,
Yvan Roux <yvan.roux@foss.st.com>,
Joel Brobecker <brobecker@adacore.com>,
Torbjorn SVENSSON <torbjorn.svensson@foss.st.com>
Cc: tom@tromey.com, gdb-patches@sourceware.org
Subject: Re: [PATCH v5] gdb/arm: Handle lazy FPU state preservation
Date: Mon, 10 Oct 2022 14:02:16 +0100 [thread overview]
Message-ID: <ce4df6e5-6bbb-40e6-ea0a-8bde67707dc1@palves.net> (raw)
In-Reply-To: <4408ece2-1850-5c1a-e267-36f266c44ec6@arm.com>
On 2022-10-10 10:26 a.m., Luis Machado wrote:
> Torbjörn has contributed a few patches now, so I think it is fair to say
> he should have Write-After-Approval permission now.
>
> It escapes me though what the process was for that.
See:
"I need an account on sourceware for git/svn/cvs write access to project
XYZ?"
at sourceware.org.
next prev parent reply other threads:[~2022-10-10 13:02 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 [this message]
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
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=ce4df6e5-6bbb-40e6-ea0a-8bde67707dc1@palves.net \
--to=pedro@palves.net \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado@arm.com \
--cc=tom@tromey.com \
--cc=torbjorn.svensson@foss.st.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).