Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-scm
Navigation:
Lists: gentoo-scm: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: "Robin H. Johnson" <robbat2@g.o>
Subject: Re: [gentoo-dev] Progress on cvs->git migration
Date: Mon, 22 Aug 2011 19:28:57 +0000
On Mon, Aug 22, 2011 at 08:28:29PM +0400, Alexey Shvetsov wrote:
> Is there any progress since last update on cvs->git migration?
The list for it is gentoo-scm, not gentoo-dev.

There's an experimental tree that mirrors CVS:
http://git-exp.overlays.gentoo.org/gitweb/?p=exp/gentoo-x86.git;a=summary

Unresolved items:
- commit signing
- thin Manifests
- merge policies

In terms of the tree size question, we were going to produce a
zero-history point at the switchover time, and offer a graftable pack
with all prior history. This got the initial packfile down under 80MiB
(with the historical packfile being ~900MiB).

-- 
Robin Hugh Johnson
Gentoo Linux: Developer, Trustee & Infrastructure Lead
E-Mail     : robbat2@g.o
GnuPG FP   : 11AC BA4F 4778 E3F6 E4ED  F38E B27B 944E 3488 4E85


Replies:
thin manifests
-- Mike Frysinger
Re: [gentoo-dev] Progress on cvs->git migration
-- Mike Frysinger
Re: Re: [gentoo-dev] Progress on cvs->git migration
-- Alexey Shvetsov
Re: Re: [gentoo-dev] Progress on cvs->git migration
-- Donnie Berkholz
References:
Progress on cvs->git migration
-- Alexey Shvetsov
Navigation:
Lists: gentoo-scm: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Progress on cvs->git migration
Next by thread:
Re: Re: [gentoo-dev] Progress on cvs->git migration
Previous by date:
Progress on cvs->git migration
Next by date:
Re: Re: [gentoo-dev] Progress on cvs->git migration


Updated May 23, 2012

Summary: Archive of the gentoo-scm mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.