From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LAHF4-0005by-ES for qemu-devel@nongnu.org; Wed, 10 Dec 2008 00:04:10 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LAHF2-0005bZ-Pd for qemu-devel@nongnu.org; Wed, 10 Dec 2008 00:04:10 -0500 Received: from [199.232.76.173] (port=37653 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LAHF2-0005bW-MX for qemu-devel@nongnu.org; Wed, 10 Dec 2008 00:04:08 -0500 Received: from mta23.gyao.ne.jp ([125.63.38.249]:28754 helo=mx.gate01.com) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LAHF0-0003dP-U1 for qemu-devel@nongnu.org; Wed, 10 Dec 2008 00:04:08 -0500 Date: Wed, 10 Dec 2008 14:02:17 +0900 From: Paul Mundt Subject: Re: [Qemu-devel] [PROPOSITION] SH4 workflow improvement Message-ID: <20081210050217.GC27356@linux-sh.org> References: <20081206120741.GB2977@game.jcrosoft.org> <200812091804.mB9I4Cxf025339@smtp11.dti.ne.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200812091804.mB9I4Cxf025339@smtp11.dti.ne.jp> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Shin-ichiro KAWASAKI , Jean-Christophe PLAGNIOL-VILLARD , Aurelien Jarno , Nobuhiro Iwamatsu On Wed, Dec 10, 2008 at 03:04:12AM +0900, takasi-y@ops.dti.ne.jp wrote: > Thank you, Jean for your effort. > > > My idea is to create a git repos to coordinate the SH4 patches > I believe this helps people testing new code easily. > It is much better than my bulk patch. > > But, as you said > > The final goal is allow us to have a patch series on which we can send > > a pull request to have it applied in the SVN > This workflow, and the person who actually apply it, is important. > Otherwise this will be a forked project, and possibly affect negatively, > discouraging people to merge sh patches to official repository. > It makes sense to have a staging tree where stuff can be queued up, tested, and reworked until it is merged upstream. For the development of new features, it is helpful to prevent fragmentation. We've already seen this with at least 3 different people working on CF at basically the same time without any knowledge of what was going on, this is something we want to avoid. In any event, I would also like to start using QEMU for other SH targets, not strictly limited to SH-4/SH-4A, which requires a bit of rework, especially for SH-2A. I've set up a git tree on kernel.org for this purpose, which will track the existing svn->git mirror that already exists. I've pulled in Kawasaki-san's changes as well: git://git.kernel.org/pub/scm/virt/qemu/lethal/qemu-sh.git I can trivially pull from Kawasaki-san also if there is new stuff there, but in general things should be going to the list directly and being applied from there. > I have added your git repos as a remote branch here, but I found I don't have > enough time to work with two repository. > So, I think I'm going to post mainly to ML even in future. > Work aimed at a staging tree is intended to be merged, not for long-term out-of-tree development. Having said that, the staging tree itself should never be in a situation where it is that badly out of sync with upstream that getting patches applied becomes problematic. Effort should certainly be concentrated on qemu-devel and the central SVN.