From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v5] gdb/hppa-tdep.c: Fix logical working flow issues and check additional store instructions
Date: Sat, 20 Dec 2014 21:07:00 -0000 [thread overview]
Message-ID: <5495E506.6000001@gmail.com> (raw)
In-Reply-To: <20141220172639.GH12884@adacore.com>
On 12/21/2014 01:26 AM, Joel Brobecker wrote:
>> 2014-12-19 Chen Gang <gang.chen.5i5j@gmail.com>
>>
>> * hppa-tdep.c (inst_saves_gr): Fix logical working flow issues
>> and check additional store instructions.
>
> Thank you. The patch looks good to me, but I don't seem to find
> a copyright assignment in file for you at the FSF. Do you happen
> to have one? Your contribution is over the 15 lines limit, and
> can therefore be considered legally significant, which is why
> we need you to have a copyright assignment on file to transfer
> the copyright of your changes over to the FSF before we can accept
> this patch.
>
OK, thanks, I shall follow the related working flow.
For me, I don't quite care about whether my contribute is appreciated,
for what I have done is only for contribution back to open source (it is
what I should do -- as a true programmer).
I mainly care about what I have done should have no negative effect with
other members, and don't waste other members' time resources.
> Let me know if you need me to send you the forms to get you started.
> It can take a while to complete.
>
Yeah, please help send the forms to me.
--
Chen Gang
Open share and attitude like air water and life which God blessed
next prev parent reply other threads:[~2014-12-20 21:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-18 21:02 Chen Gang
2014-12-20 17:26 ` Joel Brobecker
2014-12-20 21:07 ` Chen Gang [this message]
2015-01-21 10:46 ` Chen Gang S
2015-01-21 10:57 ` Joel Brobecker
2015-01-22 13:09 ` Chen Gang S
2015-01-23 7:54 ` Joel Brobecker
2015-01-23 10:04 ` Chen Gang S
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=5495E506.6000001@gmail.com \
--to=gang.chen.5i5j@gmail.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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).