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 4EEA71387FD for ; Tue, 10 Jun 2014 17:09:33 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7825FE09AB; Tue, 10 Jun 2014 17:09:28 +0000 (UTC) Received: from mail-ve0-f177.google.com (mail-ve0-f177.google.com [209.85.128.177]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 89761E090A for ; Tue, 10 Jun 2014 17:09:27 +0000 (UTC) Received: by mail-ve0-f177.google.com with SMTP id oz11so3872048veb.36 for ; Tue, 10 Jun 2014 10:09:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=8YBLYjUQd1IYYqwEjkFqoh3qfQzDNuRtT6JJWnRIPdQ=; b=l4hK+So1G8Ufy+Wfh2Et8iwrNm1aXG+LDd4w+LWoGGwb64DwhKVfVBKJZ+vVGDPT3G OL4y6Yox+AKddZGq6nAalQpvjKlHvYJDYqGh7QBVXv2jRWJGwKcGo8odXmDNWZbLEWHp Cq/y6zM2/gk5H06b8aajsMoeYDp1DFmMhi2G0K3zy9OXP5+XnoVggZt99nmRrZXvF71Y NSUvDBNT3WTx2BmpQhIfHLTpiBpdH5bLmh8PORk+z6hZiCZzgKCo0nOdAvNOssVklLl+ sXDNwwPMMFvpLmLDrBEwJCtQqnkneKmdoecUyJuibpOuN0/46+Yg1lieXiCAqDfwraZg NKGg== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.220.205.3 with SMTP id fo3mr2339680vcb.57.1402420166610; Tue, 10 Jun 2014 10:09:26 -0700 (PDT) Sender: freemanrich@gmail.com Received: by 10.52.30.227 with HTTP; Tue, 10 Jun 2014 10:09:26 -0700 (PDT) In-Reply-To: <20140610204553.7dbb98d661d265380631c6ad@gmail.com> References: <20140607201920.0e0ccd5c@gentoo.org> <53937778.7020604@sporkbox.us> <20140607230815.07bc18e7@marga.jer-c2.orkz.net> <5393B6D8.4080201@gentoo.org> <20140608135616.581807d8@marga.jer-c2.orkz.net> <53947600.50506@gentoo.org> <20140608171543.45bf6ce7@marga.jer-c2.orkz.net> <53948A21.6020809@gentoo.org> <5396106A.4010209@gentoo.org> <53962AF6.1050500@gentoo.org> <20140610194500.2185800828ffd57eb1947614@gmail.com> <539728FB.3010305@gentoo.org> <20140610204553.7dbb98d661d265380631c6ad@gmail.com> Date: Tue, 10 Jun 2014 13:09:26 -0400 X-Google-Sender-Auth: iv_Nfc-UWy2kNu_ySjv5nrEAs7A Message-ID: Subject: Re: [gentoo-dev] The state and future of the OpenRC project From: Rich Freeman To: gentoo-dev Cc: Alexander Berntsen Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: aef2ec26-a0a2-4f20-be2c-106b735943c8 X-Archives-Hash: d7346a5ee31aa3afd6dd532d52165266 On Tue, Jun 10, 2014 at 12:45 PM, Andrew Savchenko wrote: > > Why are you saying that git is inefficient with large projects? It > was developed with efficiency in mind in the first place. And > kernel guys will likely disagree with "git is not great with crazy > big projects" statement. The kernel tree that "everybody" uses has only a single committer - Linus. That is definitely a potential challenge that we may run into migrating gentoo-x86 - we have many committers and a fairly high commit rate. With Linux you have a million separate git repos and everybody cascades their changes up, which get merged into bigger and bigger patch sets. So, Linus might get a set of updates to merge from the video driver maintainer and it might contain 400 bundled commits, but it isn't like the 400 committers have direct access to Linus's tree. They all commit to their own trees and cascade up to the next level via email. We already have a working method of migrating the entire portage history to git. However, the infra tools/etc are all built around git and only a few people have access to update them. The git repository needs to make it out to the mirrors/etc. There are also a bunch of process-related details to work out. Does everybody try to rebase onto master, or do we have lots of merges? What happens if you do rebase onto master and then when you go to push it isn't a fast-forward any longer because somebody else pushed first? But, for the most part we just need to get the back-end re-written to work with a git repo. Actually migrating the tree itself to git is largely a solved problem. Rich