From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IXOQT-0007aL-Hc for qemu-devel@nongnu.org; Mon, 17 Sep 2007 17:46:41 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IXOQS-0007Zh-01 for qemu-devel@nongnu.org; Mon, 17 Sep 2007 17:46:40 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IXOQR-0007Ze-RJ for qemu-devel@nongnu.org; Mon, 17 Sep 2007 17:46:39 -0400 Received: from bangui.magic.fr ([195.154.194.245]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1IXOQR-0000hD-3x for qemu-devel@nongnu.org; Mon, 17 Sep 2007 17:46:39 -0400 Received: from [192.168.0.2] (ppp-36.net-123.static.magiconline.fr [80.118.184.36]) by bangui.magic.fr (8.13.1/8.13.1) with ESMTP id l8HLkWRA001174 for ; Mon, 17 Sep 2007 23:46:32 +0200 Subject: Re: [Qemu-devel] qemu Changelog Makefile Makefile.target TODO ae... From: "J. Mayer" In-Reply-To: <68676e00709171414j4bf64c83p8a6a01897708f1cb@mail.gmail.com> References: <1190016521.14938.148.camel@rapid> <46d6db660709170127t415b3a06vbef6c5dd19cd172f@mail.gmail.com> <1190022138.14938.153.camel@rapid> <1190027998.12960.3.camel@panther> <46d6db660709170518k9a0305as6e429669b5f1b66a@mail.gmail.com> <68676e00709171414j4bf64c83p8a6a01897708f1cb@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-15 Date: Mon, 17 Sep 2007 23:46:36 +0200 Message-Id: <1190065596.14938.203.camel@rapid> Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Mon, 2007-09-17 at 23:14 +0200, Luca wrote: > On 9/17/07, Andreas F=E4rber wrote: > > > > Am 17.09.2007 um 14:18 schrieb Christian MICHON: > > > > > On 9/17/07, Philip Boulain wrote: > > >>>>>> DON'T DO THIS KIND OF COMMIT AGAIN, PLEASE. > > >>>>> if we were using git (but you can do it locally anyway), you > > >>>>> would not > > >>>>> have these conflicts problems... > > >>>> Maybe... but Savannah uses a CVS frontend, as far as I know... > > >>> Those are excuses. > > >> > > >> So is a "you should have used X" argument. It doesn't invalidate t= he > > >> point that the commit was disruptive, and merely acts as bait for = the > > >> grand old "version repository" flamewar.* > > >> > > > > > > since I mentionned "you should have used Git", I'll repeat: > > > this commit was not disruptive to any of the Git users, and will > > > never be. > > > > > > Evolve, or prepare to be assimilated into the Collective... > > > > Both the qemu.org and the Savannah project page only mention CVS. If > > there are better ways to get the code then inform your users how to > > use that. > http://brick.kernel.dk/git/?p=3Dqemu.git;a=3Dsummary > It's tracking QEMU CVS; you're right that it's not mentioned anywhere > on the site (AFAICS). > You can also DIY with git-cvsimport; see e.g. > http://chneukirchen.org/blog/archive/2006/04/tracking-the-ruby-cvs-with= -git.html Another point is CVS is an industry standard. It has many drawbacks but is prooven to do its job as specified in a very reliable way. For now, not such a thing for git, afaik. If it ever become the new industry standard, after having prooven its reliability and long term stability, then you may be able to expect everyone to use it. Did anyone has done a long term comparison of CVS and git running on two = copies of the same production repository and have made sure that any extraction at any time of any data (ie, checkout in the present and any date in the past, diffs, ...) of the two gives exactly the same result ? Please show me such studies and I may reconsider my position... If not, you can always use it, closing your eyes and praying for everything to be OK... Regards. --=20 J. Mayer Never organized