From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001107] Support for the STMicroelectronics STR912FAW44 processor (ARM966E-S) and the Propox MMstr912 board
Date: Sat, 02 Apr 2011 00:10:00 -0000 [thread overview]
Message-ID: <20110402001007.BC50D2F7800F@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001107-104@http.bugs.ecos.sourceware.org/>
Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001107
Jonathan Larmour <jifl@ecoscentric.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jifl@ecoscentric.com
--- Comment #1 from Jonathan Larmour <jifl@ecoscentric.com> 2011-04-02 01:10:04 BST ---
Hi Jerzy,
I've just found out that your FSF copyright assignment went through.
Unfortunately the FSF don't always provide us with full details about the
assignment. For the maintainers' own records, can you confirm if you have an
employer, and if so, did they sign a copyright disclaimer? Can you also confirm
whether you completed an "assign.changes" form (which only assigns a list of
specific changes), or an "assign.future" form, which assigns a specific list of
changes, but also assigns any other contributions you make in future, without
having to fill in another assignment form?
Thanks,
Jifl
--
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2011-04-02 0:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 11:52 [Bug 1001107] New: " bugzilla-daemon
2011-04-02 0:10 ` bugzilla-daemon [this message]
2011-04-05 20:59 ` [Bug 1001107] " bugzilla-daemon
2011-04-05 22:20 ` bugzilla-daemon
2011-04-07 7:24 ` bugzilla-daemon
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=20110402001007.BC50D2F7800F@mail.ecoscentric.com \
--to=bugzilla-daemon@bugs.ecos.sourceware.org \
--cc=ecos-patches@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).