From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9191 invoked by alias); 30 Aug 2008 00:10:01 -0000 Received: (qmail 9168 invoked by uid 22791); 30 Aug 2008 00:10:00 -0000 X-Spam-Check-By: sourceware.org Received: from yx-out-1718.google.com (HELO yx-out-1718.google.com) (74.125.44.153) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 30 Aug 2008 00:09:02 +0000 Received: by yx-out-1718.google.com with SMTP id 34so600564yxf.66 for ; Fri, 29 Aug 2008 17:09:00 -0700 (PDT) Received: by 10.151.38.11 with SMTP id q11mr5108965ybj.68.1220054940461; Fri, 29 Aug 2008 17:09:00 -0700 (PDT) Received: by 10.151.98.1 with HTTP; Fri, 29 Aug 2008 17:09:00 -0700 (PDT) Message-ID: Date: Sat, 30 Aug 2008 05:31:00 -0000 From: "srinivas naga vutukuri" To: ecos-discuss@ecos.sourceware.org In-Reply-To: <20080829160552.GA23722@ubuntu.local> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080827145131.GA12261@ubuntu.local> <48B7FFC9.7040605@eCosCentric.com> <20080829160552.GA23722@ubuntu.local> 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] Looking in a future: VCS for eCos 3.0 X-SW-Source: 2008-08/txt/msg00086.txt.bz2 Why can't include git tool (which is using for linux kernel X.org etc projects) along with bzr, hg for discussion, as it also falls in the distributed version control tool. one of site, http://git.or.cz/ best regards, srinivas. On Fri, Aug 29, 2008 at 9:35 PM, Sergei Gavrikov wrote: > On Fri, Aug 29, 2008 at 02:55:21PM +0100, Jonathan Larmour wrote: >> Sergei Gavrikov wrote: >> > Hello >> > >> > It's possible it is an off-topic, but, looking in the nearest future of >> > eCos project http://sourceware.org/ml/ecos-discuss/2008-07/msg00057.html >> > I did think, It's possible, it is a good moment to change VCS (version >> > control system) for eCos development? A couple of years it was/is CVS. >> > The CVS has a well know limitations, and today, most of the developers >> > select Distributed VCS. The famous are bk, git, hg. ... I do not want >> > to fire the VCS flame here, but, if in the "eCos 3.0 planning" said >> >> A switch of VCS is probably something to tackle very soon after eCos 3.0 >> rather than before. I agree that it's time to move forward from CVS. >> >> I've had a look at Bazaar and would need a bit of convincing personally, at >> the least at this stage of its development. I found this an interesting >> read: >> http://sayspy.blogspot.com/2006/11/bazaar-vs-mercurial-unscientific.html >> (including the comments). I'm still more inclined towards Mercurial, >> although SVN is an obvious possibility just really due to its more >> widespread use and slightly better client support (in addition both of >> which are available on sourceware.org, but Bazaar isn't). But I'd really >> really prefer to have something distributed. >> >> When the time comes, we can see what it looks like then. The decision isn't >> just mine of course. > > Jonathan, thank you for your responce! I have become to think what I > will be alone voter :-) I would vote for either mercurial or bazaar. > Both are Distributed VCS, both are cross-platforms, both are written in > Python (but mercurial has `diff' is written in C, so, `hg' did penalty > `bzr' in 2006, bzr'2008 is faster). I would not vote for SVN, just > thinking: If it is elder, therefore, it is more stable and clever. I > found again what I read about bazaar's strength in 2007 from Mark > Shuttleworth http://www.markshuttleworth.com/archives/123 (with the > comments). It is interesting to read too. Thank you for your link. > > Sergei > > -- > Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos > and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss > > -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss