From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 31 09:24:41 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2FB6416A417 for ; Thu, 31 Jan 2008 09:24:41 +0000 (UTC) (envelope-from wundram@beenic.net) Received: from mail.beenic.net (mail.beenic.net [83.246.72.40]) by mx1.freebsd.org (Postfix) with ESMTP id DC8E213C43E for ; Thu, 31 Jan 2008 09:24:40 +0000 (UTC) (envelope-from wundram@beenic.net) Received: from [192.168.1.38] (a89-182-148-8.net-htp.de [89.182.148.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.beenic.net (Postfix) with ESMTP id 61236A44529; Thu, 31 Jan 2008 10:24:20 +0100 (CET) From: "Heiko Wundram (Beenic)" Organization: Beenic Networks GmbH To: freebsd-hackers@freebsd.org Date: Thu, 31 Jan 2008 10:25:54 +0100 User-Agent: KMail/1.9.7 References: <78cb3d3f0801302245v2183c613t6ecdd9acebbe9ef7@mail.gmail.com> <47A1700B.3090406@gmail.com> <47A18EDA.4040501@elischer.org> In-Reply-To: <47A18EDA.4040501@elischer.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200801311025.55412.wundram@beenic.net> Cc: Adrian Penisoara , "Aryeh M. Friedman" , Julian Elischer Subject: Re: [OT] Q: what would you choose for a VCS today X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2008 09:24:41 -0000 Am Donnerstag, 31. Januar 2008 10:03:22 schrieb Julian Elischer: > I'm having to use mercurial. > I'm not really enjoying it. > works ok for small projects. BSD is a bit big for it. > doe work foe offline editing, but loses all your BSD history. We're using mercurial pretty much for all of our (100,000+ SLOC) repositories, and I cannot agree that it's only appropriate for small projects. As mercurial is a distributed RCS, the hard part in using it is you have to impose some policies, esp. related to merging changes back into a "central" repository, which aren't required for "centralized" systems like CVS and subversion, but from my view, the added benefit for a developer in using a distributed revision control system is well worth the extra effort in writing (and thinking) up the policies once. mercurial (at least by default) doesn't allow you to create remote branches anyway (in pushing back changes to the central store), so the policies you might have are effectly enforced by the system anyway. YMMV, of course, and mercurial has its defects (primary checkout/cloning of a large repository from a central store takes ages, at least over a slow link, the last time I had to do this [but I don't know if any progress has been made there]), but for me, it's been working fine for the daily needs I have as a developer. -- Heiko Wundram Product & Application Development