public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Luis Machado <luis.machado@arm.com>
To: Joel Brobecker <brobecker@adacore.com>,
	Yvan Roux <yvan.roux@foss.st.com>
Cc: 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:35:27 +0100	[thread overview]
Message-ID: <a4dc576f-a372-cfd8-9237-bdf079e3cfd5@arm.com> (raw)
In-Reply-To: <Y0QxLhfH+7SThi1Q@adacore.com>

On 10/10/22 15:50, Joel Brobecker via Gdb-patches wrote:
>>> For the avoidance of doubt, Luis is maintainer for arm and AArch64,
>>> so when he says it's good for him, it means the patch is approved
>>> for pushing ;-).
>>
>> Yes thanks for the heads up, I pushed the patch last Friday.
> 
> I see; thanks for confirming.
> 
> It used to be that we asked people to send a quick reply to the approval
> email to confirm that the commit was pushed.  In the absence of a review
> tool that keeps track of patches, I have found this to be quite useful
> to keep track.

A bit off-topic for this patch, but personally I've been using the IRC bot to keep track of this, so
I don't mind as much. Besides, quite a bit of GDB chat goes on in there. Maybe patchworks can keep
track of it as well.

> 
>>> I don't see you in the list of contributors who have "Write After
>>> Approval" privileges. Do all the authors of the patch have an FSF
>>> copyright assignment on file? I checked the record, but didn't
>>> find anything...
>>
>> Torbjorn and I are covered by STMicro copyright assignement, so it
>> should be fine.
> 
> Nice!
> 

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.

  reply	other threads:[~2022-10-10 16:35 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 [this message]
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=a4dc576f-a372-cfd8-9237-bdf079e3cfd5@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).