public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: John Dallaway <john@dallaway.org.uk>
To: "Choi, David" <David.Choi@micrel.com>
Cc: "Li, Charles" <Charles.Li@micrel.com>,
	        eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: Re: submit process
Date: Wed, 07 Apr 2010 07:16:00 -0000	[thread overview]
Message-ID: <4BBC3136.9080105@dallaway.org.uk> (raw)
In-Reply-To: <C43529A246480145B0A6D0234BDB0F0D481CD9@MELANITE.micrel.com>

Hi David

Choi, David wrote:

> Based on your suggestion, I filled [the assignment request form] and
> sent it to assign@gnu.org last week.
> 
> But I have not received any feedback until today. I want to check the
> status. What should I do?

The FSF will prepare a copyright assignment document and send it to you
by the regular postal service. This can sometimes take a while. I would
not assume that the process has failed just yet.

> Is it possible to submit my driver before finishing [process of
> copyright assignment]?

Yes, feel free to submit the driver. It may be of use to other eCos
users in advance of the copyright assignment.

John Dallaway
eCos maintainer

      reply	other threads:[~2010-04-07  7:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <C43529A246480145B0A6D0234BDB0F0D481CAC@MELANITE.micrel.com>
     [not found] ` <4B6BD6D8.3010906@dallaway.org.uk>
     [not found]   ` <C43529A246480145B0A6D0234BDB0F0D481CAD@MELANITE.micrel.com>
     [not found]     ` <4B6C5F41.5020000@dallaway.org.uk>
     [not found]       ` <C43529A246480145B0A6D0234BDB0F0D481CD3@MELANITE.micrel.com>
2010-03-29 16:01         ` boot loader John Dallaway
2010-04-07  0:17           ` submit process Choi, David
2010-04-07  7:16             ` John Dallaway [this message]

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=4BBC3136.9080105@dallaway.org.uk \
    --to=john@dallaway.org.uk \
    --cc=Charles.Li@micrel.com \
    --cc=David.Choi@micrel.com \
    --cc=ecos-maintainers@ecos.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).