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: Thu, 07 Apr 2011 07:24:00 -0000 [thread overview]
Message-ID: <20110407072416.CA2922F80003@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
--- Comment #4 from Jerzy Dyrda <jerzdy@gmail.com> 2011-04-07 08:24:13 BST ---
(In reply to comment #3)
> (In reply to comment #2)
> > (In reply to comment #1)
Hello Jifl,
> What I mean is that the form you were given may have had a name:
> "assign.future". If it doesn't,
>
I'm afraid that it doesn't have "assign.future".
> then maybe you can just tell me whether it
> assigned just existing changes, or existing _and_ future changes. That way we
> know whether it just covers the work you did,
> or whether we can accept other
> contributions from you in the future without filling in a separate copyright
> assignment.
Yes, of course. That will be nice - no special copyright assignment per new
contribution. Especially that next work i.e. driver for ETH on STM32 is waiting
to push to community.
Best regard,
jerzy
--
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.
prev parent reply other threads:[~2011-04-07 7:24 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 ` [Bug 1001107] " bugzilla-daemon
2011-04-05 20:59 ` bugzilla-daemon
2011-04-05 22:20 ` bugzilla-daemon
2011-04-07 7:24 ` bugzilla-daemon [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=20110407072416.CA2922F80003@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).