public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: "Richard Rauch" <rrauch@itrgmbh.de>
To: <ecos-devel@sourceware.org>
Subject: AW: Port Contribution
Date: Thu, 12 May 2011 10:22:00 -0000	[thread overview]
Message-ID: <CF47B23262FE4BD2AD72F6D05D1369B7@DESKTOPITRGMBH> (raw)
In-Reply-To: <D6050C555CC56940A7AF32652283027603F03C21@mail2.STMIRV01.COM>

Thanks for the fast reply.

I know this review process. Our port is based on this port, too.
So maybe it would be better to await the results of this review, before
contributing our own port?
But unfortunately there is less progress on this task.  


Hi Richard,

This is what I know about the contribution process:

#1 To submit contributions, you need your copyright assignment from the FSF
in place: http://ecos.sourceware.org/assign.html

#2 Patches should be submitted using Bugzilla
(http://bugs.ecos.sourceware.org/), setting the Component field to Patches
and contributions. Even if it is obsolete, I still put the eCos patch
mailing list in CC of the Bugzilla case.

#3 Check this post for eCos coding style:
http://ecos.sourceware.org/ml/ecos-devel/2011-03/msg00016.html

#4 As commented by Ilija, it is better to submit diff in plain text format
(http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001219)

#5 Changes in ecos.db are not sent as diff. Submit an ecos.db than contains
only your added entries.

#6 Note that there is a work in progress to add ARM9 support to eCos:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000819

Christophe

-----Original Message-----
From: ecos-devel-owner@ecos.sourceware.org
[mailto:ecos-devel-owner@ecos.sourceware.org] On Behalf Of Richard Rauch
Sent: 12. mai 2011 08:25
To: ecos-devel@sourceware.org
Subject: Port Contribution

Hi all,

We have finished now our announced port to Atmel ARM9 microcontroller
AT91SAM9.
Next we want to contribute this port.

We have a lot of questions how to do this:

How we have to prepare the software?
Where we have to upload?
Is there any paper work to do?

We will need some assistance for this process. It is the first time, that we
contributing to the ecos community!
 
Thanks

Richard

 
Richard Rauch
email: rrauch@itrgmbh.de
_______________________________________________

ITR GmbH
Informationstechnologie Rauch
Schnepfenreuther Hauptstrasse 27b
D-90425 Nuernberg
_______________________________________________


  reply	other threads:[~2011-05-12 10:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-12  6:25 Richard Rauch
2011-05-12  8:42 ` Christophe Coutand
2011-05-12 10:22   ` Richard Rauch [this message]
2011-05-13  7:52   ` Ilija Kocho
2011-05-13  8:30     ` Sergei Gavrikov

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=CF47B23262FE4BD2AD72F6D05D1369B7@DESKTOPITRGMBH \
    --to=rrauch@itrgmbh.de \
    --cc=ecos-devel@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).