From: John Dallaway <john@dallaway.org.uk>
To: ricky wu <rickleaf.wu@gmail.com>
Cc: eCos Patches List <ecos-patches@ecos.sourceware.org>
Subject: Re: ecos for arm qemu is okey
Date: Fri, 25 Mar 2011 14:57:00 -0000 [thread overview]
Message-ID: <4D8CAD43.6010600@dallaway.org.uk> (raw)
In-Reply-To: <AANLkTikdFjTLsC_MFL75Hrxa-4MNJp9uHT6zTQVZKMiL@mail.gmail.com>
Hi Ricky
ricky wu wrote:
>> 2011/3/25 John Dallaway <john@dallaway.org.uk>:
>>
>>> Are you interested in contributing your eCos Mini2440 platform port to
>>> the eCos project?
>
> of course, i am pleasure.
Great!
To be clear, your Mini2440 port will be subject to review by the eCos
maintainers, just like any other contribution to the eCos project.
> But, which method i will use.
>
> Our project is hg repositories and it is newest,
> You can clone it directory.
>
> Do you need i send a mini2440 package.
We need to be sure that the code you are contributing is precisely
defined. At present, our preferred method is for the contributor to
create a new Bugzilla report at:
http://bugs.ecos.sourceware.org
Set the "Component" field to "Patches and Contributions". Then attach a
diff file relative to the current eCos project sources which contains
your new port. Something like "diff -r -U5 -N" or the Mercurial equivalent.
You will also need to complete a copyright assignment to the FSF:
http://ecos.sourceware.org/assign.html
It looks like you are the only person who has worked on this port. If
there are others who have contributed, they will all need to assign
copyright.
Please let me know if anything is not clear.
John Dallaway
eCos maintainer
http://www.dallaway.org.uk/john
prev parent reply other threads:[~2011-03-25 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-25 13:28 ricky wu
2011-03-25 14:32 ` John Dallaway
[not found] ` <AANLkTikdFjTLsC_MFL75Hrxa-4MNJp9uHT6zTQVZKMiL@mail.gmail.com>
2011-03-25 14:57 ` 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=4D8CAD43.6010600@dallaway.org.uk \
--to=john@dallaway.org.uk \
--cc=ecos-patches@ecos.sourceware.org \
--cc=rickleaf.wu@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).