From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9846 invoked by alias); 31 Oct 2009 10:00:51 -0000 Received: (qmail 9838 invoked by uid 22791); 31 Oct 2009 10:00:50 -0000 X-SWARE-Spam-Status: No, hits=-1.4 required=5.0 tests=AWL,BAYES_20 X-Spam-Check-By: sourceware.org Received: from mtaout02-winn.ispmail.ntl.com (HELO mtaout02-winn.ispmail.ntl.com) (81.103.221.48) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 31 Oct 2009 10:00:46 +0000 Received: from aamtaout04-winn.ispmail.ntl.com ([81.103.221.35]) by mtaout02-winn.ispmail.ntl.com (InterMail vM.7.08.04.00 201-2186-134-20080326) with ESMTP id <20091031100043.ZYKG27507.mtaout02-winn.ispmail.ntl.com@aamtaout04-winn.ispmail.ntl.com>; Sat, 31 Oct 2009 10:00:43 +0000 Received: from cog.dallaway.org.uk ([213.106.93.52]) by aamtaout04-winn.ispmail.ntl.com (InterMail vG.2.02.00.01 201-2161-120-102-20060912) with ESMTP id <20091031100043.JAPC22934.aamtaout04-winn.ispmail.ntl.com@cog.dallaway.org.uk>; Sat, 31 Oct 2009 10:00:43 +0000 Received: from cog.dallaway.org.uk (cog.dallaway.org.uk [127.0.0.1]) by cog.dallaway.org.uk (8.13.8/8.13.8) with ESMTP id n9VA0b8O021089; Sat, 31 Oct 2009 10:00:37 GMT Message-ID: <4AEC0AC5.2060208@dallaway.org.uk> Date: Sat, 31 Oct 2009 10:00:00 -0000 From: John Dallaway User-Agent: Thunderbird 2.0.0.22 (X11/20090625) MIME-Version: 1.0 To: Ilija Stanislevik CC: ecos-devel@ecos.sourceware.org Subject: Re: Ethernet over SPI driver for ENC424J600 References: <4AE546ED.3000303@siva.com.mk> <4AE56642.20201@dallaway.org.uk> <4AE5857B.6020309@siva.com.mk> <4AE5904C.8080502@dallaway.org.uk> <4AE9D38D.1030806@siva.com.mk> In-Reply-To: <4AE9D38D.1030806@siva.com.mk> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Mailing-List: contact ecos-devel-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-devel-owner@ecos.sourceware.org X-SW-Source: 2009-10/txt/msg00067.txt.bz2 Ilija Stanislevik wrote: > John Dallaway wrote: > >> The main ideas behind project registration are to encourage >> collaboration on new eCos components, to minimise duplicated effort and >> to allow for early feedback from the eCos maintainers. With this mind, >> we would expect: >> >> a) contribution of the code to eCos CVS when it is ready (subject to >> review by the eCos maintainers and copyright assignment to FSF) >> >> b) sharing of your pre-release code with others in the eCos community on >> request >> >> c) responsiveness to feedback from the community > > Hi John, > > We decided to register this project. Great. Thank you, Ilija. John Dallaway