From owner-freebsd-git@freebsd.org Sat Feb 25 00:36:52 2017 Return-Path: Delivered-To: freebsd-git@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4579FCECF94 for ; Sat, 25 Feb 2017 00:36:52 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [88.98.225.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "msa1.earth.yoonka.com", Issuer "msa1.earth.yoonka.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id DF687F9F for ; Sat, 25 Feb 2017 00:36:51 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from ultrabook.yoonka.com (ip-109-84-3-58.web.vodafone.de [109.84.3.58]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id v1M8BHXn030417 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Wed, 22 Feb 2017 08:11:22 GMT (envelope-from list1@gjunka.com) X-Authentication-Warning: msa1.earth.yoonka.com: Host ip-109-84-3-58.web.vodafone.de [109.84.3.58] claimed to be ultrabook.yoonka.com Subject: Re: Reconsider switching from svn to git? To: freebsd-git@freebsd.org References: <49da18e4-b211-c48d-5486-368cda912fc0@multiplay.co.uk> <86mvdfy3qs.fsf@desk.des.no> From: Grzegorz Junka Message-ID: <562a721d-731d-5302-a2c9-df51d0328124@gjunka.com> Date: Wed, 22 Feb 2017 08:11:12 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-git@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussion of git use in the FreeBSD project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Feb 2017 00:36:52 -0000 On 22/02/2017 00:46, Ed Maste wrote: > On 21 February 2017 at 18:47, Warner Losh wrote: >> For small commits, I agree. For longer lived project branches, >> however, there can be issues. Specifically, in svn, when you delete a >> branch, it just marks it as empty, but you can get back to it at any >> point in the branch. In git, however, deleting a branch deletes the >> meta-data needed to get back to the branch (as does rebasing). We'd >> need some way to administratively prohibit this, perhaps, for the >> source of truth repo. I have no clue if this is possible with git, >> just putting it out there. > Ok, we could easily disallow any destructive activity on a > source-of-truth git repo, including force (non-fast-forward) pushes > and branch deletion. This could be also easily solved by having a backup server with restricted access. The main server could be a remote for that backup server. Then the backup server wold periodically pull all changes (git fetch main_server). This would backup all branches ever pushed to the remote server. Grzegorz