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 841CC13838B for ; Tue, 7 Oct 2014 07:57:58 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 030F2E08EB; Tue, 7 Oct 2014 07:57:57 +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 F2228E08AC; Tue, 7 Oct 2014 07:57:55 +0000 (UTC) Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com [209.85.212.180]) (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 A7932340340; Tue, 7 Oct 2014 07:57:54 +0000 (UTC) Received: by mail-wi0-f180.google.com with SMTP id em10so6998192wid.7 for ; Tue, 07 Oct 2014 00:57:52 -0700 (PDT) X-Received: by 10.180.24.35 with SMTP id r3mr2483883wif.71.1412668672083; Tue, 07 Oct 2014 00:57:52 -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; Tue, 7 Oct 2014 00:57:32 -0700 (PDT) In-Reply-To: <20141006104858.18b07b10@pomiot.lan> References: <21554.11562.674143.286256@a1i15.kph.uni-mainz.de> <20141006104858.18b07b10@pomiot.lan> From: Dirkjan Ochtman Date: Tue, 7 Oct 2014 09:57:32 +0200 Message-ID: Subject: Re: [gentoo-project] Council / Git Migration Agenda To: gentoo-project@lists.gentoo.org Cc: Ulrich Mueller , gentoo-scm@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: ab824ecc-1a83-4a39-8880-c40771c82262 X-Archives-Hash: c1edca43d0416a05105301c4ebed0776 On Mon, Oct 6, 2014 at 10:48 AM, Micha=C5=82 G=C3=B3rny = wrote: > I was thinking of prepending the old history via 'git replace' in > the gitweb repo to allow looking back. However, that idea has > the downside that users would be confused by having past commits in > gitweb yet not in clones. > > Kent improved my idea suggesting that we use a separate repo for that > 'complete history' view. That is, we would have three repos: > > 1. history.git -- with past CVS history up to conversion, > > 2. dev.git -- with history starting with conversion, > > 3. joined-history.git -- dev.git with 'git replace' for history.git, > that is the complete history including both pre- and post-conversion > commits. Can we do that without requiring the git replace stuff? E.g. have dev.git be a shallow clone of a joined-history.git? Cheers, Dirkjan