qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: qemu-devel@nongnu.org
Cc: Shin-ichiro KAWASAKI <kawasaki@juno.dti.ne.jp>,
	Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
	Aurelien Jarno <aurelien@aurel32.net>,
	Nobuhiro Iwamatsu <iwamatsu.nobuhiro@renesas.com>
Subject: Re: [Qemu-devel] [PROPOSITION] SH4 workflow improvement
Date: Wed, 10 Dec 2008 14:02:17 +0900	[thread overview]
Message-ID: <20081210050217.GC27356@linux-sh.org> (raw)
In-Reply-To: <200812091804.mB9I4Cxf025339@smtp11.dti.ne.jp>

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.

  reply	other threads:[~2008-12-10  5:04 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
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 [this message]
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=20081210050217.GC27356@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=aurelien@aurel32.net \
    --cc=iwamatsu.nobuhiro@renesas.com \
    --cc=kawasaki@juno.dti.ne.jp \
    --cc=plagnioj@jcrosoft.com \
    --cc=qemu-devel@nongnu.org \
    /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).