From: Adam Renquinha <arenquinha@cimeq.qc.ca>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: Fredrik Hederstierna <fredrik.hederstierna@verisure.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix exception unwinding for ARM Cortex-M
Date: Fri, 23 Sep 2016 17:32:00 -0000 [thread overview]
Message-ID: <2ed4bdc4-3168-acba-0382-9cea822c7032@cimeq.qc.ca> (raw)
In-Reply-To: <CAH=s-PMMsZeqfhkaQG-yunP1a1MT5Yyn=Y2snPum+bVAypgkGg@mail.gmail.com>
FYI, the assignment process is done for me as well as for Fredrik. The
patch can be submitted.
James-Adam Renquinha Henri, Ing. jr
Ingénieur d'application
CIMEQ INC.
Le 2016-08-09 à 05:16, Yao Qi a écrit :
> On Fri, Aug 5, 2016 at 8:01 PM, Adam Renquinha <arenquinha@cimeq.qc.ca> wrote:
>>
>> Hmm, if I understand correctly, I should e-mail one of the gdb maintainers
>> to get the assignment to fill? You did that before; how it went?
>
> You can follow this, and use the third form (request-assign.future)
> https://sourceware.org/gdb/wiki/ContributionChecklist#FSF_copyright_Assignment
>
next prev parent reply other threads:[~2016-09-23 16:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 8:13 Fredrik Hederstierna
2016-07-29 11:47 ` Yao Qi
2016-08-02 9:43 ` Fredrik Hederstierna
2016-08-02 16:01 ` Yao Qi
2016-08-03 10:56 ` Fredrik Hederstierna
2016-08-03 11:19 ` Yao Qi
2016-08-03 17:33 ` James-Adam Renquinha Henri
2016-08-04 7:04 ` Fredrik Hederstierna
2016-08-05 19:02 ` Adam Renquinha
2016-08-09 9:17 ` Yao Qi
2016-09-23 17:32 ` Adam Renquinha [this message]
2016-09-26 3:03 ` Yao Qi
2016-09-27 1:38 ` Adam Renquinha
2016-09-27 4:40 ` Yao Qi
[not found] <AM4PR1001MB0948AC4D9CB635F5A9A2FC82EFDC0@AM4PR1001MB0948.EURPRD10.PROD.OUTLOOK.COM>
[not found] ` <HE1PR1001MB130613C0995C4C21A630373BEF1B0@HE1PR1001MB1306.EURPRD10.PROD.OUTLOOK.COM>
2019-06-10 21:25 ` James-Adam Renquinha Henri
2019-06-12 9:01 ` Alan Hayward
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=2ed4bdc4-3168-acba-0382-9cea822c7032@cimeq.qc.ca \
--to=arenquinha@cimeq.qc.ca \
--cc=fredrik.hederstierna@verisure.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.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).