Re: [Qemu-devel] [PROPOSITION] SH4 workflow improvement

[Nobuhiro Iwamatsu <iwamatsu.nobuhiro@renesas.com>]

Shin-ichiro KAWASAKI wrote:
> Kristoffer Ericson wrote:
>> On Sat, 6 Dec 2008 13:07:41 +0100
>> Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com> wrote:
>>
>>> Hi all,
>>>
>>> 	Actually it's difficult to work on the improvement of SH4
>>> 	because we do not have a place to work.
>> I've noticed the same, the main qemu repository 
>> doesn't contain much in the way of SH4. Seems to
>> take awhile to get stuff applied upstreams.
> 
> I have same thought, also.
> 
>>> 	My idea is to create a git repos to coordinate the SH4 patches
>>>
>>> 	I propose this because I've try to test different patch send to the ML
>>> 	and it's difficult because you can not apply them simply to generate a
>>> 	patch series suitable.
>>>
>>> 	For this I've create a git here
>>> 	http://uboot.jcrosoft.org/git?p=qemu-sh4.git;a=summary
>>>
>>> 	If you have a better place to put I've no problem with it.
>>>
>>> 	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
>>>
>>> 	Takashi YOSHII, Shin-ichiro KAWASAKI I've try to merge your patches on
>>> 	this tree please take a look and tell me if I do something wrong
> 
> I think it is one of the good ideas.  I'm trying the git repository. Thanks.
> 
> And I wonder why the merges of SH4 patches to the upstream are slow.
> My guess is that the sent patches are not reviewed enough, and main QEMU developers
> are too busy to spare time for them.  Reviewing on SH4 related patches by QEMU-SH4
> developers might be a help.  Any comments on this idea?
> 
I also think so.
I agree with management with Git.
However, it is necessary to think the patch is managed
and it is taken up-stream.
I think that it will do the fork the way things are going.
We might have it commit up-stream by deciding the manager of SH.

Best regards,
 Nobuhiro