From owner-freebsd-security@FreeBSD.ORG Wed Nov 21 00:41:07 2012 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 79CAFFDD; Wed, 21 Nov 2012 00:41:07 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: from mail-ea0-f182.google.com (mail-ea0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id 733618FC14; Wed, 21 Nov 2012 00:41:06 +0000 (UTC) Received: by mail-ea0-f182.google.com with SMTP id a14so1347965eaa.13 for ; Tue, 20 Nov 2012 16:41:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=a2qUeBhYJcVqm/vWaf/MxxA39D9XaLvFlXyjJ3FpUPU=; b=ESwbhsbrlxE4XzSU+N78XfG3itpBuxjhnh4SlpnsneeYXmojeT+E5ZKAMnBXS5gyCn 3n0sw0PYtGL/F6UZTZp8vuZULewO1ngNCYUMTwLfP+P+Rl0ZABz99/Jh/ptj6pQEB615 /Ken8TgwK3iZwD5iHyoFj63OvZupvGHbt6812ZdzbK77AZK5VcSoax6gNnMbAXo7G6ol 0bhsPRyG/1OV+Qo6gOFW8A0xfnYEB29QD+qgfsIorPJyR3l52PoQhTaYvIgNiaePgVSJ bznkKn3qp6CGSpWwhX+GPdM9QEhmc4ohFrHhYFYRYWKz/4xCCUXPvPK2nnMex+E30amJ 0j6Q== Received: by 10.14.216.193 with SMTP id g41mr39367451eep.37.1353458465269; Tue, 20 Nov 2012 16:41:05 -0800 (PST) Received: from ithaqua.etoilebsd.net (ithaqua.etoilebsd.net. [37.59.37.188]) by mx.google.com with ESMTPS id 2sm33788564eef.17.2012.11.20.16.41.03 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 20 Nov 2012 16:41:04 -0800 (PST) Sender: Baptiste Daroussin Date: Wed, 21 Nov 2012 01:41:02 +0100 From: Baptiste Daroussin To: Zach Leslie Subject: Re: FreeBSD needs Git to ensure repo integrity [was: 2012 incident] Message-ID: <20121121004102.GQ71195@ithaqua.etoilebsd.net> References: <20121117221143.41c29ba2@nonamehost> <50AA2A6C.8060604@gmail.com> <20121120030813.GB38037@zjl.local> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="G6ArjEZjY3m60389" Content-Disposition: inline In-Reply-To: <20121120030813.GB38037@zjl.local> User-Agent: Mutt/1.5.21 (2010-09-15) X-Mailman-Approved-At: Wed, 21 Nov 2012 02:16:56 +0000 Cc: Alexander Yerenkow , "C. P. Ghost" , freebsd-hackers@freebsd.org, Volodymyr Kostyrko , freebsd-security@freebsd.org, Ivan Voras , freebsd-questions@freebsd.org X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Nov 2012 00:41:07 -0000 --G6ArjEZjY3m60389 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 19, 2012 at 07:08:13PM -0800, Zach Leslie wrote: > > http://www.fossil-scm.org/ > >=20 > > I'm not fossil user, but it's BSD licensed in written in C. > > Baptise Daroussin probably could tell us more about fossil pro and cons. >=20 > This misses one of of the main points raised in the original post. The > proliferation of git as a revision control system. >=20 > Also, this particular tool bails out on the unix philosophy, with its web > gui, ticket tracker etc. Do one thing. Do it well. >=20 Look at the internal of fossil and how things are done in fossil and you wo= uld understand that the last sentence is totally wrong. Fossil has really nice features that could nicely fits with FreeBSD workflo= ws and greatly improves it. It has most of the new shiny feature everyone can expect from a dvcs, but it also has it drawbacks: The converted repositories (I did convert docs, src and ports) with full hi= story kept: branches, tags, etc. is huge and the first clone would be painful to = do. On the other side you have multiple working copies open on the same clone w= hich is really nice. Some of the operations can be slow, J=F6rg Sonnenberger wrote an analysis a= bout this one the fossil wiki, but don't remember the link sorry. =46rom my testing, apart from the do we really need a new scm question? I a= m a big fan of fossil and find it easier and cleaner than all the other scm I know,= I use git for pkgng and other projects, I use a lot mercurial on some other a= rea, and fossil remains my favorite :). But I really don't think it could fit FreeBSD's requirements as it is now. but there are lots of room of improvem= ents. The learning curve to fossil is probably really easy. On of the last thing is that fossil lacks keyword expansion. That said I'm happy with svn on FreeBSD, I still from time to time do conve= rsion of out different tree to fossil for fun, but no more and I won't advocate f= or any vcs change. Bapt --G6ArjEZjY3m60389 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlCsIx4ACgkQ8kTtMUmk6ExNdQCeOyKnCwMEgLgxzYvhc291sQen c3cAnjTrPoy2qLq4wd9QHtU+9zjb366B =eJAx -----END PGP SIGNATURE----- --G6ArjEZjY3m60389--