From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24118 invoked by alias); 12 Sep 2003 10:19:07 -0000 Mailing-List: contact ecos-maintainers-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: ecos-maintainers-owner@sources.redhat.com Received: (qmail 24107 invoked from network); 12 Sep 2003 10:19:05 -0000 Date: Fri, 12 Sep 2003 10:19:00 -0000 From: Andrew Lunn To: Jani Monoses Cc: ecos-maintainers@sources.redhat.com Subject: Re: [RFC] lwip officially in ecos? Message-ID: <20030912101855.GB347@biferten.ma.tech.ascom.ch> References: <20030912121452.5c29331b.jani@iv.ro> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030912121452.5c29331b.jani@iv.ro> User-Agent: Mutt/1.4i X-Filter-Version: 1.11a (rubicon) X-SW-Source: 2003-09/txt/msg00015.txt.bz2 On Fri, Sep 12, 2003 at 12:14:52PM +0300, Jani Monoses wrote: > Hello all > > I'd like to ask the maintainers' opinion on putting lwIP in ecos CVS. My opinion is that its a good idea. It complements the other two stacks well and people do use it. How actively is the base of lwIP being developed. One down side of integrating it into eCos, is that new developments of the upstream package take longer to get into the eCos version. As it is now, people will import the latest version into there own trees rather than use a potentially old version in eCos. What would be good is if you could put some scripts into the eCos package which automagically updated the eCos version with the latest from Savanna. It then becomes a case of running the script and then the test cases before committing it to the eCos repository. jffs2 works like this. Andrew