From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29455 invoked by alias); 31 Mar 2013 22:33:13 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 29438 invoked by uid 89); 31 Mar 2013 22:33:05 -0000 X-Spam-SWARE-Status: No, score=-0.2 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,MIME_QP_LONG_LINE,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 Received: from outbound002.roc2.bluetie.com (HELO outbound002.roc2.bluetie.com) (208.89.132.142) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Sun, 31 Mar 2013 22:33:03 +0000 Received: from web005.roc2.bluetie.com ([10.200.2.99]) by outbound002.roc2.bluetie.com with outbound002 id JNZ11l00228AQ4S01NZ1ik; Sun, 31 Mar 2013 18:33:01 -0400 X-CMAE-OUT-Analysis: v=2.0 cv=Lc2+G0ji c=1 sm=1 a=Fq2dLNikPEoA:10 a=i-wQWBNYtOgA:10 a=IkcTkHD0fZMA:10 a=FmX3VfpdAAAA:8 a=QoHJ8kPOAAAA:8 a=onvgoMsWCgMA:10 a=X2n7lVjMG4QA:10 a=su_n_wKUkhR60omNz1AA:9 a=QEXdDO2ut3YA:10 a=uTg3uDTdO3UBl-aA:21 a=0Sq8UzXpjwn6XLf4:21 a=vL3HbRNXJhJQQ3qw5A4SiA==:117 X-CMAE-OUT-Score: 0.00 Received: from web005.roc2.bluetie.com (localhost.localdomain [127.0.0.1]) by web005.roc2.bluetie.com (Postfix) with ESMTP id 4256CE90125 for ; Sun, 31 Mar 2013 18:33:01 -0400 (EDT) Message-ID: <20130331183301.17691@web005.roc2.bluetie.com> X-HTTP-Received: from kenkyee.excite [64.145.41.116] by web005.roc2.bluetie.com (BlueTie WebMail ); Sun, 31 Mar 2013 18:33:01 -0400 Date: Sun, 31 Mar 2013 22:33:00 -0000 Cc: To: ecos-discuss@sourceware.org From: "Ken Yee" Content-transfer-encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Subject: [ECOS] Re: Is eCosPro a fork of eCos? X-SW-Source: 2013-03/txt/msg00073.txt.bz2 I haven't posted to this list in a while, but I still get it in digest form= for some reason. Just wanted to say that either eCosPro or eCosCentric holding back bug fixe= s from the main tree should not be done. You guys should do the consulting thing and create new packages, etc. to st= ack on top of eCos to make money,=20 but IMHO leaving known bugs unfixed so you can tell customers "we have many= hard won bugs fixed if you buy our product" isn't a good way to keep the e= cosystem alive. People will try eCos and hit the bugs and say it's crap...= they won't say "maybe we should have tried the 'Pro' version because it's l= ess buggy". I project I was on was killed off because there were too many bugs w/ the n= etworking stack and PPP.=20=20 And IMHO, yes, anything where you take a copy of the mainline and only keep= your own copy of it to fix or add features to is obvously a fork...that's = the basic definition of a fork.... -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss