From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 19 13:13:02 2012 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id ACAC1CC2; Mon, 19 Nov 2012 13:13:02 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id AF2558FC17; Mon, 19 Nov 2012 13:13:01 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA13807; Mon, 19 Nov 2012 15:13:00 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1TaR9o-000CYq-3v; Mon, 19 Nov 2012 15:13:00 +0200 Message-ID: <50AA305A.8080702@FreeBSD.org> Date: Mon, 19 Nov 2012 15:12:58 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121030 Thunderbird/16.0.2 MIME-Version: 1.0 To: Nathan Whitehorn Subject: Re: FreeBSD needs Git to ensure repo integrity [was: 2012 incident] References: <20121117221143.41c29ba2@nonamehost> <50a8eb34.5pMwq6kSsi47QgKI%perryh@pluto.rain.com> <20121118073128.GG73505@kib.kiev.ua> <50A9912E.3090608@freebsd.org> In-Reply-To: <50A9912E.3090608@freebsd.org> X-Enigmail-Version: 1.4.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@FreeBSD.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Nov 2012 13:13:02 -0000 on 19/11/2012 03:53 Nathan Whitehorn said the following: > git would be a huge step backward from svn for the central repo in lots of ways. Dramatic statements ("huge", "lots") require dramatic evidence. > Besides being (in my experience) extremely fragile and error-prone and the Ditto ("extremely"). > issues of workflow that have been brought up, the loss of monotonic revision > numbers is a really major problem. Monotonic revision numbers are nice to have, but again, are they really of that major importance? > Switching SCMs as a result of a security > problem is also an action totally disproportionate with the issue that should > not be made in a panic. Having more [cryptographic] verifiability in the release > process is a good thing; it is not strictly related to the choice of version > control system. With this part I entirely agree. -- Andriy Gapon