From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1NVZ7V-00045d-5c for garchives@archives.gentoo.org; Thu, 14 Jan 2010 23:28:53 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1953DE0CB6; Thu, 14 Jan 2010 23:28:45 +0000 (UTC) Received: from mail-pw0-f47.google.com (mail-pw0-f47.google.com [209.85.160.47]) by pigeon.gentoo.org (Postfix) with ESMTP id D354DE0CB6 for ; Thu, 14 Jan 2010 23:28:44 +0000 (UTC) Received: by pwj10 with SMTP id 10so4564003pwj.26 for ; Thu, 14 Jan 2010 15:28:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=Oghf5qunFzo2mRAdTNurVzMt2XDhx8xR87DFWn2EIuU=; b=Y5zeFI4JHsmVP+q3cpGZbwZ7eOGcBXkTENbkqvmLn0T6HYIlmSbmO804NvpdKNHhBT YCtfpy6EYx57gtyTP3TCvf7K3P44R/QcLTHSo19ksePK3MUBh2z+hfFgtNIVUu4cNpnm a/4hRjIFvViJgBGWCg4YPp7h+XOwJ3iggFEZk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=k7CK59uxVi1+0XLLS6/8k+WDz5dbE47TLIdGthb6l+NW1kPGtKvlv9zILq0r5Zc3Ei PlsDPBNePbJAJGsA4KhSjU0sPFKix3jD/JHuiwFf9Y9gGPkocX32VRuEBO0y8yONMTL2 qdBnj1q3J0qsT3pIv/yvTSL820R1obKydx4iE= 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 Sender: nirbheek.chauhan@gmail.com Received: by 10.115.117.5 with SMTP id u5mr1014484wam.111.1263511724218; Thu, 14 Jan 2010 15:28:44 -0800 (PST) In-Reply-To: <20100114225420.GF16921@orbis-terrarum.net> References: <201001112305.16532.hwoarang@gentoo.org> <201001122149.11091.hwoarang@gentoo.org> <201001131054.03953.vapier@gentoo.org> <8b4c83ad1001140449k49995e0ra01eeca16167735a@mail.gmail.com> <4B4F7F1B.4080902@the-cell.co.uk> <8b4c83ad1001141421y22e416b8q4e5e4c9d47f4821f@mail.gmail.com> <8b4c83ad1001141429w33558119o9a19059ae181475b@mail.gmail.com> <20100114225420.GF16921@orbis-terrarum.net> Date: Fri, 15 Jan 2010 04:58:44 +0530 X-Google-Sender-Auth: 5674c820f0b454c1 Message-ID: <8b4c83ad1001141528h6ae4da4dyc50c46de1cfd1c37@mail.gmail.com> Subject: Re: [gentoo-dev] proxy maintainership and gentoo-x86 scm From: Nirbheek Chauhan To: gentoo-dev@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: f644a4bd-efac-4e3b-8303-4801c0ee33f2 X-Archives-Hash: 31032fda90ef4c02f9c20f1b960ee0a6 On Fri, Jan 15, 2010 at 4:24 AM, Robin H. Johnson wrote: > On Fri, Jan 15, 2010 at 03:59:00AM +0530, Nirbheek Chauhan wrote: >> ChangeLog (-13,000 which would be redundant, and should be >> auto-generated alongwith metadata prior to distribution via rsync. >> Hey, this is something that needs to be done too!) > ChangeLog != commit logs. > > There is frequently additional information in the CVS commit messages > that isn't in the ChangeLogs. ChangeLogs aren't always updated reliably > either, esp for ebuild cleanups (hi vapier). > All the more reason to just chuck manual ChangeLogs in favour of auto-generated ones. Atleast, that's what gnome projects do since they moved to git [ http://live.gnome.org/Git/ChangeLog ]. However, this will entail a change in how commit messages are formatted; git commit messages need to be very different from CVS/svn ones. > The actual performance of git itself isn't the largest problem. > The migration issues, esp. the speed of the conversion are. > > My status of the migration side itself hasn't changed since the end of > October: > http://archives.gentoo.org/gentoo-scm/msg_e0a0a41200c1fc6a0fda68b4ff9d2c61.xml > > That top item is the largest blocker. The actual conversion time is down > to 9 hours, but with more than that again in setting it up. I'd like to > get the conversion time down to UNDER 4 hours. It's mostly > single-threaded, and we've got lots of cores available, it just needs > parallelization. We're basically dead in the water during the > conversion, there is NO incremental support at all. > Actually, this has confused me for a while. Sorry if this is a dumb question, but why do we care about the conversion speed if we can just convert it once, make the old cvs repo read-only and be done with it? Are we concerned about the window during which cvs access will have to be blocked and devs will sit around twiddling thumbs? > Side-project to the above: Is there anything link Psyco for Python > acceleration that works on 64-bit machines? Psyco itself has a warning > on the frontpage of no 64-bit support. > I had written Pysco off as dead and started looking forward to Unladen Swallow :) http://code.google.com/p/unladen-swallow/wiki/ProjectPlan > We DO still need somebody that cares about CVS access to test with > git-cvssserver against the existing conversion. > This will fit in quite badly with the proposed changes to make Manifest have only distfile manifests when using git, and to not have ChangeLogs for the simple reason that they (Manifests and ChangeLogs) invariably cause merge conflicts. And then there was also the plan to not edit headers for files to prevent extra commits (which are even more useless in git). -- ~Nirbheek Chauhan Gentoo GNOME+Mozilla Team