From: Pedro Alves <palves@redhat.com>
To: Will Huang <will.huang@aliyun-inc.com>
Cc: Yao Qi <yao@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH][PR threads/15824] when get threads name failed from info threads with linux kernel version earlier than 2.6.33
Date: Fri, 16 Aug 2013 16:24:00 -0000 [thread overview]
Message-ID: <520E5233.6030005@redhat.com> (raw)
In-Reply-To: <520E0CFB.9010203@codesourcery.com>
Hi!
Thanks. Do you have your copyright assignment on file? We
will need it before we can accept the changes. See
<http://sourceware.org/gdb/wiki/ContributionChecklist>.
If you haven't filed it yet, please contact me off-list and I
can send you the forms.
(I haven't really looked at the patch.)
--
Pedro Alves
next prev parent reply other threads:[~2013-08-16 16:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 4:27 Will Huang
2013-08-16 2:26 ` Yao Qi
2013-08-16 5:32 ` Will Huang
2013-08-16 9:38 ` Yao Qi
2013-08-16 10:22 ` Will Huang
2013-08-16 11:29 ` Yao Qi
2013-08-16 16:24 ` Pedro Alves [this message]
2013-08-19 2:52 ` Will Huang
2013-08-19 3:10 ` Yao Qi
2013-08-19 5:01 ` Will Huang
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=520E5233.6030005@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=will.huang@aliyun-inc.com \
--cc=yao@codesourcery.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