From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1LX0W0-00049O-B0 for garchives@archives.gentoo.org; Tue, 10 Feb 2009 21:51:36 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id BA09CE038E; Tue, 10 Feb 2009 21:51:35 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 972ADE038E for ; Tue, 10 Feb 2009 21:51:35 +0000 (UTC) Received: from gentoo.org (xray.science.oregonstate.edu [128.193.220.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id 1882B66401 for ; Tue, 10 Feb 2009 21:51:35 +0000 (UTC) Date: Tue, 10 Feb 2009 13:51:34 -0800 From: Donnie Berkholz To: gentoo-council@lists.gentoo.org Subject: [gentoo-council] DVCS update Message-ID: <20090210215134.GE3692@comet> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-council@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="qOrJKOH36bD5yhNe" Content-Disposition: inline User-Agent: Mutt/1.5.18 (2008-05-17) X-Archives-Salt: fe689f5d-e3e8-46f7-95cc-4c3aa4a53ea9 X-Archives-Hash: 9681c403879d66738efe6f4dec3e543e --qOrJKOH36bD5yhNe Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi all, Here's a quick update on the git-migration experiment. We've pretty much=20 settled on doing one large repository for the entire tree for a couple=20 of reasons: - It's realistic to complete in the short term: It doesn't require a=20 level of rearchitecture that will delay it forever. The alternative of=20 one repo per package requires changes to many of our tools, and=20 enhancements to git of varying scopes. - Many of the biggest problems with it have been solved. For example,=20 this week I found a tool that should retain history when merging a=20 package in an overlay to the main tree, even if there is no common=20 ancestry. - The remaining problems are not blockers. For example, there is no way=20 to check out just part of a tree. Disk space isn't so hard to find now=20 that this is a requirement. - Robin has commented that he doesn't know what kind of server-side=20 resources are required. I've talked to a number of git admins=20 (kernel.org, fedora, freedesktop.org, gnome), and they have all said the=20 hardware requirements for git are negligible. They don't have any=20 resource on their servers that's being used up. It's gitweb that is=20 somewhat resource-intensive. The next thing I can think of that needs to happen is putting together a=20 concrete plan for how a migration would work and making sure all=20 necessary tools support it, on all sides: developer, user, and=20 infrastructure. We've got portage support now, but I don't have any idea=20 what needs to change on the backend infra servers. --=20 Thanks, Donnie Donnie Berkholz Developer, Gentoo Linux Blog: http://dberkholz.wordpress.com --qOrJKOH36bD5yhNe Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEABECAAYFAkmR9uYACgkQXVaO67S1rtvQRgCg509SxZcJzolqUnFHn8ciML1O Gg0AoL/KDL93k+8/A9y/d0yeEo1SYC4i =cpjs -----END PGP SIGNATURE----- --qOrJKOH36bD5yhNe--