From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id DDF2313838B for ; Sun, 5 Oct 2014 08:18:47 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 02A95E08F3; Sun, 5 Oct 2014 08:18:46 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 05D2EE08CE; Sun, 5 Oct 2014 08:18:45 +0000 (UTC) Received: from mail-wg0-f43.google.com (mail-wg0-f43.google.com [74.125.82.43]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: djc) by smtp.gentoo.org (Postfix) with ESMTPSA id AE9A03402CC; Sun, 5 Oct 2014 08:18:44 +0000 (UTC) Received: by mail-wg0-f43.google.com with SMTP id m15so4319379wgh.26 for ; Sun, 05 Oct 2014 01:18:41 -0700 (PDT) X-Received: by 10.180.19.193 with SMTP id h1mr10746360wie.14.1412497121451; Sun, 05 Oct 2014 01:18:41 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Project discussion list X-BeenThere: gentoo-project@lists.gentoo.org Reply-To: gentoo-project@lists.gentoo.org MIME-Version: 1.0 Received: by 10.27.203.135 with HTTP; Sun, 5 Oct 2014 01:18:21 -0700 (PDT) In-Reply-To: References: From: Dirkjan Ochtman Date: Sun, 5 Oct 2014 10:18:21 +0200 Message-ID: Subject: Re: [gentoo-project] Council / Git Migration Agenda To: gentoo-project@lists.gentoo.org Cc: gentoo-scm@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: 892d771a-b0bb-40d4-bf37-59d8a80bc75a X-Archives-Hash: b2567f0bbe0b54dda1e6d540d92202a2 On Sat, Oct 4, 2014 at 2:00 AM, Rich Freeman wrote: > I was thinking that it might make more sense to just make things > really simple and ONLY migrate the active tree into the starting git > repository. That is, basically take the rsync tree, remove metadata, > and do a git init. (Then follow that up with removing changelogs, > cleaning up cvs headers, and so on.) > > A historical migration could be done in parallel and released a few > hours later. However, it would not be a contiguous repository. That > is, the converted active tree commit would not have any parents. If > you wanted to have a contiguous tree you would need to splice in the > historical migration with git replace. I think that would be sad. IMO there should be full history to the default tree (even if we advocate shallow clones by default). Yes, the history might not be perfect; people can splice in an improved history later with git replace. I would be disappointed if the git hash for the default tree doesn't represent (some version of) the full history. Cheers, Dirkjan