From: Michael Snyder <msnyder@specifix.com>
To: Tea <teawater@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: about copyright assignment
Date: Wed, 23 Apr 2008 20:10:00 -0000 [thread overview]
Message-ID: <1208973582.4615.181.camel@localhost.localdomain> (raw)
In-Reply-To: <daef60380804221919x42b2fa84gdc0e103d0f333d09@mail.gmail.com>
On Wed, 2008-04-23 at 10:19 +0800, Tea wrote:
> Hi Michael and Thiago,
>
> I send mail to "assign@gnu.org" twice to ask how to deal with "FSF
> copyright assignment
> in place". But I didn't get response from they. Maybe they are busy.
> Could you please help me something about "FSF copyright assignment in
> place"?
Well, they're volunteers, so they aren't always terribly prompt.
Give it some time, you should hear from them before long.
By the way, it isn't necessary to Cc: me or Thiago when
you write to the gdb list. We both follow the list.
Thanks, and keep on posting your questions. ;-)
next prev parent reply other threads:[~2008-04-23 18:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 5:03 Tea
2008-04-23 20:10 ` Michael Snyder [this message]
2008-04-24 8:48 ` Tea
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=1208973582.4615.181.camel@localhost.localdomain \
--to=msnyder@specifix.com \
--cc=gdb-patches@sourceware.org \
--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