From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17990 invoked by alias); 22 Sep 2009 11:41:30 -0000 Received: (qmail 17891 invoked by uid 22791); 22 Sep 2009 11:41:30 -0000 X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40 X-Spam-Check-By: sourceware.org Received: from cpanel5.proisp.no (HELO cpanel5.proisp.no) (209.85.100.29) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 22 Sep 2009 11:41:27 +0000 Received: from an-out-0708.google.com ([209.85.132.249]:18991) by cpanel5.proisp.no with esmtpsa (TLSv1:RC4-MD5:128) (Exim 4.69) (envelope-from ) id 1Mq3kL-0004tn-JH for ecos-discuss@ecos.sourceware.org; Tue, 22 Sep 2009 13:41:25 +0200 Received: by an-out-0708.google.com with SMTP id b6so1746337ana.21 for ; Tue, 22 Sep 2009 04:41:25 -0700 (PDT) MIME-Version: 1.0 Received: by 10.101.43.12 with SMTP id v12mr846647anj.90.1253619685020; Tue, 22 Sep 2009 04:41:25 -0700 (PDT) In-Reply-To: <20090922112443.GA20692@sg-ubuntu.local> References: <4AB7900D.30204@ecoscentric.com> <4AB80124.3080708@ecoscentric.com> <87hbuvwbg1.fsf@thor.barco.com> <4AB8B021.8070408@ecoscentric.com> <20090922112443.GA20692@sg-ubuntu.local> Date: Tue, 22 Sep 2009 11:41:00 -0000 Message-ID: From: Edgar Grimberg To: Sergei Gavrikov Cc: Alex Schuilenburg , Peter Korsgaard , ecos-discuss@ecos.sourceware.org Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes 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 Subject: Re: [ECOS] Re: Switching to using git on eCosForge X-SW-Source: 2009-09/txt/msg00192.txt.bz2 Hi, My 2 cents on the topic: * eCos maintainers need to follow up on patches and bugs. The kernel and other "common" areas should have priority over specific HALs. This is a place where things must go without any hiccups. I've been around the office when Oyvind found the sscanf bug. Imagine the frustration finding a 2 years old patch just rotting out there... Maybe a clear procedure must be written and published. Something like in the emergency rooms: sever bugs - one day to commit, normal bugs in common areas - 3 days to commit, normal bugs in HAL - 7 days to commit, silly problems - 14 days to commit. * no matter what source control to use, it is a must to be easy for the maintainers to use it. The regular users will be able, with a command described somewhere on the web, to get all the sources. The "super-"users to send patches will able to find a way to do so no matter what source control system will be chosen (also a command or two on the webpages can help a lot in that regard). Regards, Edgar -- Edgar Grimberg System Developer Zylin AS ZY1000 JTAG Debugger http://www.zylin.com/zy1000.html Phone: (+47) 51 63 25 00 -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss