From: Shin-ichiro KAWASAKI <kawasaki@juno.dti.ne.jp>
To: Kristoffer Ericson <kristoffer.ericson@gmail.com>
Cc: Nobuhiro Iwamatsu <iwamatsu.nobuhiro@renesas.com>,
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
qemu-devel@nongnu.org, Aurelien Jarno <aurelien@aurel32.net>,
takasi-y@ops.dti.ne.jp
Subject: Re: [Qemu-devel] [PROPOSITION] SH4 workflow improvement
Date: Mon, 08 Dec 2008 01:39:44 +0900 [thread overview]
Message-ID: <493BFC50.9070506@juno.dti.ne.jp> (raw)
In-Reply-To: <20081206143719.6f2d209a.kristoffer.ericson@gmail.com>
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?
Regards,
Shin-ichiro KAWASAKI
next prev parent reply other threads:[~2008-12-07 16:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-06 12:07 [Qemu-devel] [PROPOSITION] SH4 workflow improvement Jean-Christophe PLAGNIOL-VILLARD
2008-12-06 13:37 ` Kristoffer Ericson
2008-12-07 16:39 ` Shin-ichiro KAWASAKI [this message]
2008-12-09 2:21 ` Nobuhiro Iwamatsu
2008-12-07 23:24 ` Jean-Christophe PLAGNIOL-VILLARD
2008-12-09 18:04 ` takasi-y
2008-12-10 5:02 ` Paul Mundt
2008-12-11 16:24 ` Shin-ichiro KAWASAKI
2008-12-16 7:07 ` Paul Mundt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=493BFC50.9070506@juno.dti.ne.jp \
--to=kawasaki@juno.dti.ne.jp \
--cc=aurelien@aurel32.net \
--cc=iwamatsu.nobuhiro@renesas.com \
--cc=kristoffer.ericson@gmail.com \
--cc=plagnioj@jcrosoft.com \
--cc=qemu-devel@nongnu.org \
--cc=takasi-y@ops.dti.ne.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).