From: Jonathan Larmour <jifl@eCosCentric.com>
To: Vitali Fridliand <vitali.fridliand@gmail.com>
Cc: ecos-maintainers@ecos.sourceware.org
Subject: Re: Code contribution
Date: Thu, 17 Apr 2008 13:24:00 -0000 [thread overview]
Message-ID: <48074F3F.80209@eCosCentric.com> (raw)
In-Reply-To: <b44791530804170553n1f077b60i3f72dd9bb7fd9908@mail.gmail.com>
Vitali Fridliand wrote:
> Dear maintainers,
>
> I have made a port of eCOS Redboot to ST Microelectronics SPEArNet MCU.
> The port includes Redboot RAMROM configuration, ROM configuration,
> ethernet driver for the integrated MAC110, serial driver for the
> integrated RS323.
>
> How it would be possible to contribute the port to the code base?
Hi Vitali,
The first step to get out of the way is getting a copyright assignment in
place with the Free Software Foundation (FSF). To request the assignment
form, you need to first fill in the form at this link:
<http://cvs.savannah.gnu.org/viewvc/gnulib/doc/Copyright/request-assign.future?revision=1&root=gnulib>
and email it to <assign@gnu.org>.
We should get notified when the process is complete, after which we can
look at getting the contribution incorporated. You can either create the
contribution in our bugzilla database (http://bugs.ecos.sourceware.org> or
mail it to <ecos-patches@ecos.sourceware.org>. For large bodies of new
code, probably the best thing to do is send the new files in a tarball, and
any changes as a patch (usually created by something like "cvs -q diff -u5
-p").
You may find this useful:
http://ecos.sourceware.org/patches-criteria.html
http://ecos.sourceware.org/patches-generating.html
and if submitting via bugzilla:
http://ecos.sourceware.org/patches-submitting.html
Jifl
--
eCosCentric Limited http://www.eCosCentric.com/ The eCos experts
** Visit us at ESC Silicon Valley <http://www.embedded.com/esc/sv> **
** April 15-17 2008, Booth 3012, San Jose McEnery Convention Center **
Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["Si fractum non sit, noli id reficere"]------ Opinions==mine
prev parent reply other threads:[~2008-04-17 13:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b44791530804170551p1a173535yccecccccd598bfa8@mail.gmail.com>
2008-04-17 12:53 ` Vitali Fridliand
2008-04-17 13:24 ` Jonathan Larmour [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=48074F3F.80209@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=ecos-maintainers@ecos.sourceware.org \
--cc=vitali.fridliand@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).