public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@eCosCentric.com>
To: aladdin <sp0500@gmail.com>
Cc: ecos-maintainers@ecos.sourceware.org
Subject: Re: How to commit an new CPU port to eCos CVS
Date: Mon, 15 Oct 2007 12:46:00 -0000	[thread overview]
Message-ID: <4713610C.1040809@eCosCentric.com> (raw)
In-Reply-To: <74a282130710102332x77b9b4ffjef99345dddea5c04@mail.gmail.com>

aladdin wrote:
> Dear Sir,
> 
> We had just ported eCos to our own RISC, S+core,  and wondering how to
> commit it to eCos CVS ?

Hi,

Thanks for contributing back.

A guide to submitting changes to eCos is here: 
<http://ecos.sourceware.org/patches.html>. Although in fact some of what is 
described at that link has been overtaken by recent events, so that instead 
of assigning copyright to eCosCentric, it is now required to assign 
copyright to the Free Software Foundation (FSF). This copyright assignment 
is a requirement in order for the FSF to defend eCos from license abuses.

To request an assignment form, please fill in the form in the following 
link and e-mail it to <assign@gnu.org>:
http://cvs.savannah.gnu.org/viewvc/gnulib/doc/Copyright/request-assign.future?revision=1&root=gnulib 


Hope this helps,

Jifl
-- 
eCosCentric Limited      http://www.eCosCentric.com/     The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK.       Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
  >>>> Visit us on stand 810 at The Embedded Systems Show 2007, NEC <<<<
  >>>> Oct 17-18 Birmingham, UK http://www.edaexhibitions.com/ess/  <<<<
------["The best things in life aren't things."]------      Opinions==mine

      reply	other threads:[~2007-10-15 12:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-11  6:32 aladdin
2007-10-15 12:46 ` 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=4713610C.1040809@eCosCentric.com \
    --to=jifl@ecoscentric.com \
    --cc=ecos-maintainers@ecos.sourceware.org \
    --cc=sp0500@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).