From: Pedro Alves <palves@redhat.com>
To: Hui Zhu <teawater@gmail.com>
Cc: Hui Zhu <hui_zhu@mentor.com>,
gdb-patches@sourceware.org, Yao Qi <Yao_Qi@mentor.com>
Subject: Re: Fix error when gdb connect to a stub that tracepoint is running[1/2] Add a flag initialized to struct trace_status
Date: Tue, 13 Mar 2012 13:46:00 -0000 [thread overview]
Message-ID: <4F5F4F9C.2080601@redhat.com> (raw)
In-Reply-To: <CANFwon380xd44uRZtQsvNzn4ATTvOcsuyJ6TsHV=3jt=R+FRYA@mail.gmail.com>
On 03/11/2012 04:12 PM, Hui Zhu wrote:
> Hi Pedro,
>
> I had made sure that the FSF acknowledged my copyright assignment mid
> february. So this email is OK now.
I consulted with the FSF copyright clerk, and I was told your paperwork
isn't fully sort out yet, so you can't yet transfer changes on behalf of
Mentor. You can however contribute your own independent changes
meanwhile (under your personal assignment), as there's trust that Mentor
is good about getting their paperwork in regularly. In this particular case,
I've gone ahead and checked in the patches. But again, please let's make
sure the paperwork is fully done before you can transfer changes on
behalf of Mentor.
> And I found that this issue affect 7.4 too. I suggest commit this
> patch to 7.4 branch too.
It'd be good to have a testcase. ;-) I'm not sure if 7.4 has all the
bits necessary? I'll check it out.
--
Pedro Alves
next prev parent reply other threads:[~2012-03-13 13:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 14:47 Hui Zhu
2012-03-01 18:26 ` Pedro Alves
2012-03-01 18:49 ` Pedro Alves
2012-03-05 2:26 ` Hui Zhu
2012-03-11 16:13 ` Hui Zhu
2012-03-13 13:46 ` Pedro Alves [this message]
2012-03-13 22:21 ` Pedro Alves
2012-03-20 18:50 ` Fix tracepoints in extended-remote mode regression (Re: Fix error when gdb connect to a stub that tracepoint is running[1/2] Add a flag initialized to struct trace_status) Pedro Alves
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=4F5F4F9C.2080601@redhat.com \
--to=palves@redhat.com \
--cc=Yao_Qi@mentor.com \
--cc=gdb-patches@sourceware.org \
--cc=hui_zhu@mentor.com \
--cc=teawater@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