public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: John Dallaway <john@dallaway.org.uk>
To: Bernd Edlinger <bernd.edlinger@softing.com>
Cc: ecos-maintainers@ecos.sourceware.org
Subject: Re: eCos port for Atmel AT91SAM9G45 and similar processors
Date: Wed, 22 Aug 2012 19:49:00 -0000	[thread overview]
Message-ID: <503537C2.5030708@dallaway.org.uk> (raw)
In-Reply-To: <3a3995a2-83d1-4ed0-a8f9-9ac34867e24a@bhv.softing.com>

Bernd

On 21/08/12 13:23, Bernd Edlinger wrote:

> over the last weeks I tried to enter all Softing patches of the eCos O/S to the
> Bugzilla, which might be of general interest. This work is now complete.
> 
> As you know, the Atmel AT91SAM9G45 Port was begun by Richad Rauch over two years ago,
> Softing and I added other cool features over the last year too. Actually I expected
> Richard to contribute this Port by end of last year, but unfortunately he has lost
> the interest in that matter. Therefore I decided not to wait any longer.

Thank you for your mail and for taking the time to prepare these
contributions.

In additional to the necessary technical review, all contributions must
be accompanied by a copyright assignment to the FSF before they can be
included in the eCos repository. Details at:

    http://ecos.sourceware.org/assign.html

We would need copyright assignments from yourself and from others within
Softing who have contributed to the development. We would also need an
assignment from Richard Rauch. Do you envisage any issues with obtaining
the necessary assignments from the developers within Softing?

John Dallaway
eCos maintainer
http://www.dallaway.org.uk/john

      reply	other threads:[~2012-08-22 19:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-21 12:24 Bernd Edlinger
2012-08-22 19:49 ` 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=503537C2.5030708@dallaway.org.uk \
    --to=john@dallaway.org.uk \
    --cc=bernd.edlinger@softing.com \
    --cc=ecos-maintainers@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).