From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9539 invoked by alias); 14 Oct 2011 16:47:22 -0000 Received: (qmail 9521 invoked by uid 22791); 14 Oct 2011 16:47:16 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,TW_BZ X-Spam-Check-By: sourceware.org Received: from smtp.nokia.com (HELO mgw-sa01.nokia.com) (147.243.1.47) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 14 Oct 2011 16:47:02 +0000 Received: from gar.localnet (berwst16747.europe.nokia.com [172.25.167.47]) by mgw-sa01.nokia.com (Switch-3.4.4/Switch-3.4.3) with ESMTP id p9EGktc3010160; Fri, 14 Oct 2011 19:46:56 +0300 From: =?iso-8859-1?q?Andr=E9_P=F6nitz?= To: Eli Zaretskii Subject: Re: GIT and CVS Date: Fri, 14 Oct 2011 16:59:00 -0000 User-Agent: KMail/1.13.5 (Linux/2.6.35-30-generic; KDE/4.5.5; i686; ; ) Cc: gdb@sourceware.org References: <201110141435.59962.andre.poenitz@nokia.com> <8339evlkq2.fsf@gnu.org> In-Reply-To: <8339evlkq2.fsf@gnu.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201110141846.54990.andre.poenitz@nokia.com> X-Nokia-AV: Clean X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2011-10/txt/msg00146.txt.bz2 On Friday 14 October 2011 16:19:01 ext Eli Zaretskii wrote: > [..] It goes without saying that a modern dVCS is better than CVS in many > ways. But switching to a dVCS does not necessarily mean git, there > are alternatives. For example, bisecting is supported by bzr and > Mercurial as well. > > So please don't make it sound like the only 2 choices are CVS and git. You are right, there are more dVCS options. My restriction to git was however intentional, as this was the topic of the thread and Phil's original question and also what the non-cvs-using gdb developers actually use. Moreover it's something I use, and feel sort of comfortable with. I don't think changing the direction into a generic "what VCS is best" discussion would be helpful. At best, we would come up with the same conclusion as everyone else in such discussions, namely that there is no single best VCS system. I think this is all about making the life of the people who actually write the code easier. Right now it looks like they are mostly comfortable with git. Might not be the perfect choice in some people's opinion, but why care? Even if they wanted to use IP over Avian Carriers because they _know_ it makes them more productive I'd see no reason to discuss packet loss rates ;-} Don't let the perfect be the enemy of the good. Using git is so much of a step forward compared to CVS that I can't imagine _any_ difference between git and other dVCSs to obliterate the gain of going from CVS to git. Andre' PS: Btw, during my "personal" switch to git I also found the need to type two commands instead of one rather annoying. I ended up with a handful shell functions like 'gp' for "git stash; git pull --rebase; git stash pop". Not sure whether this is good practice, but it certainly solved that "problem".