From: "Terry Guo" <terry.guo@arm.com>
To: "'Yao Qi'" <yao@codesourcery.com>
Cc: "'Eli Zaretskii'" <eliz@gnu.org>, <gdb-patches@sourceware.org>
Subject: RE: [PATCH]Fix that GDB will get hang on Windows when using pipe to get stdout and stderr from stub
Date: Mon, 16 Jul 2012 06:55:00 -0000 [thread overview]
Message-ID: <000501cd6320$20421f40$60c65dc0$@guo@arm.com> (raw)
In-Reply-To: <1883057.PpQhSjGyFQ@qiyao.dyndns.org>
Hi Yao,
Thanks for reminding. I signed a FSF copyright assignment when I started to work for GCC. But I can't remember its content. Do you know whether it cover the GDB and Binutils by default?
BR,
Terry
> -----Original Message-----
> From: Yao Qi [mailto:yao@codesourcery.com]
> Sent: Monday, July 16, 2012 8:38 PM
> To: gdb-patches@sourceware.org
> Cc: Terry Guo; Eli Zaretskii
> Subject: Re: [PATCH]Fix that GDB will get hang on Windows when using
> pipe to get stdout and stderr from stub
>
> On Monday, July 16, 2012 01:52:23 PM Terry Guo wrote:
> > Sorry to bother you again. I realized I haven't gdb write permission.
> Could
> > you please help me to commit it at your convenient time? The
> attachment is
> > the patch against the latest gdb trunk.
>
> Terry,
>
> As your patch can't go in as an obvious change, you need a FSF
> copyright
> assignment. Please contact to Tom or Joel to get the form, and fill in
> it.
> Usually, it takes weeks or one month, I think. Once your assignment
> paper is
> ready, you or other people can check in your patch to CVS trunk.
>
> In parallel, you can apply for a sourceware account for writing access.
>
> http://sourceware.org/cgi-bin/pdw/ps_form.cgi
>
> You need a person (global maintainer, I think) to approve your request.
>
> --
> Yao (齐尧)
next prev parent reply other threads:[~2012-07-16 6:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000001cd5338$ded61b20$9c825160$%guo@arm.com>
[not found] ` <000501cd5404$fbf210c0$f3d63240$%guo@arm.com>
2012-06-27 3:06 ` Eli Zaretskii
2012-06-27 16:54 ` Eli Zaretskii
2012-07-04 8:19 ` Terry Guo
2012-07-11 5:00 ` Terry Guo
[not found] ` <000301cd59bd$ce1c8900$6a559b00$%guo@arm.com>
[not found] ` <000101cd5f22$2371cdc0$6a556940$%guo@arm.com>
2012-07-11 18:36 ` Eli Zaretskii
2012-07-12 1:41 ` Terry Guo
[not found] ` <000301cd5fcf$838d31b0$8aa79510$%guo@arm.com>
2012-07-12 5:20 ` Eli Zaretskii
2012-07-16 5:51 ` Terry Guo
2012-07-17 1:28 ` Sergio Durigan Junior
2012-07-17 3:05 ` Terry Guo
2012-07-17 7:51 ` Terry Guo
2012-07-17 17:21 ` Sergio Durigan Junior
2012-07-16 6:08 ` Terry Guo
2012-07-16 6:38 ` Yao Qi
2012-07-16 6:55 ` Terry Guo [this message]
2012-07-16 7:19 ` Yao Qi
2012-07-16 8:10 ` Terry Guo
2012-06-26 1:12 Terry Guo
2012-06-27 1:33 ` Terry Guo
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='000501cd6320$20421f40$60c65dc0$@guo@arm.com' \
--to=terry.guo@arm.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).