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 29BEA198005 for ; Wed, 27 Feb 2013 02:05:19 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 17E0FE0642; Wed, 27 Feb 2013 02:05:17 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 8869EE0642 for ; Wed, 27 Feb 2013 02:05:16 +0000 (UTC) Received: from [192.168.1.210] (unknown [24.86.176.233]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: dolsen) by smtp.gentoo.org (Postfix) with ESMTPSA id 488F233DD1A for ; Wed, 27 Feb 2013 02:05:15 +0000 (UTC) Message-ID: <1361930694.3997.297.camel@big_daddy.dol-sen.ca> Subject: Re: [gentoo-catalyst] patch, fix broken seed stage update From: Brian Dolbec To: gentoo-catalyst@lists.gentoo.org Date: Tue, 26 Feb 2013 18:04:54 -0800 In-Reply-To: References: <1361895645.3997.269.camel@big_daddy.dol-sen.ca> <512CF0E4.70000@gentoo.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.6.3 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-catalyst@lists.gentoo.org Reply-to: gentoo-catalyst@lists.gentoo.org Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Archives-Salt: d82d390b-2733-41ff-9484-c5842dbc5621 X-Archives-Hash: d458a3b7baf58c89282b78d348e1d1eb On Tue, 2013-02-26 at 11:39 -0800, Matt Turner wrote: > On Tue, Feb 26, 2013 at 9:29 AM, Rick "Zero_Chaos" Farina > wrote: > > In my opinion you can kill the current catalyst 3 branch as nothing uses > > it and afaik it doesn't work. jmbvicetto should be able to > > authoritatively agree or not. > > If Brian's work is to be the basis for future revisions of catalyst, > it should be the master branch. We can branch current master as a > stable branch. The current catalyst2 branch is totally dead, and > overwriting it doesn't cause us to lose anything. > I generally agree that my rewrite should become the master branch, but it could live in a side branch for a while longer, there are many more changes needed to clean up the code. It is likely to be broken at times some commits by themselves won't be complete, etc... > ... but the patches should be sent to the list (with git > format-patch/send-email) and reviewed before being committed to > master. > I tried using git to send this patch, but it did not work. I'll look into how to make it work with email. But I do question the need to send all patches to this list for review. Take this patch email for instance. It was primarily for the last commit I did to fix the update_seed methods which I found not working correctly. I also mentioned I had rebased all my other work, condensing where it made sense... Do you see any code suggestions, questions and/or comments in regards to it... NO All mails in this thread are about everything else :/ I will continue to spam the list with all my rebased commits, which I intended to do when I had more time. I sent this one off this morning before I went to work. I know Jorge was interested in the changes. I'm back now, so will manually prepare more patch mails.