From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IXOfY-00056c-9q for qemu-devel@nongnu.org; Mon, 17 Sep 2007 18:02:16 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IXOfW-00055j-KF for qemu-devel@nongnu.org; Mon, 17 Sep 2007 18:02:15 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IXOfW-00055c-DR for qemu-devel@nongnu.org; Mon, 17 Sep 2007 18:02:14 -0400 Received: from rv-out-0910.google.com ([209.85.198.188]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IXOfV-0004cG-Qw for qemu-devel@nongnu.org; Mon, 17 Sep 2007 18:02:14 -0400 Received: by rv-out-0910.google.com with SMTP id g11so5526895rvb for ; Mon, 17 Sep 2007 15:02:12 -0700 (PDT) Message-ID: <68676e00709171502y6f3718b5k9d5aed15cf68e7f6@mail.gmail.com> Date: Tue, 18 Sep 2007 00:02:12 +0200 From: Luca Subject: Re: [Qemu-devel] qemu Changelog Makefile Makefile.target TODO ae... In-Reply-To: <1190065596.14938.203.camel@rapid> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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> <1190065596.14938.203.camel@rapid> 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 9/17/07, J. Mayer wrote: > On Mon, 2007-09-17 at 23:14 +0200, Luca wrote: > > > > 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=qemu.git;a=summary > > 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? Actually CVS doesn't provide _any_ guarantee about data integrity. GIT does. So... > 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... ...yes, I'm willing to trust GIT over CVS any time ;) Luca