All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Christoph Hellwig <hch@lst.de>,
	Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
	Qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Merging qemu-iotests into qemu.git?
Date: Mon, 20 Feb 2012 17:42:25 +0100	[thread overview]
Message-ID: <4F4277F1.4080109@redhat.com> (raw)
In-Reply-To: <20120216205310.GA29156@lst.de>

Am 16.02.2012 21:53, schrieb Christoph Hellwig:
> On Thu, Feb 16, 2012 at 04:01:58PM +0100, Kevin Wolf wrote:
>> Hi Christoph,
>>
>> I just talked to Stefan about our testing, both regarding the block
>> layer and qemu in general, and we came to the conclusion that it would
>> probably make sense to merge qemu-iotests into qemu.git.
>>
>> The immediate benefit would be that we could include some short-running
>> tests into 'make check'. Long-term we would profit from being in the
>> same tests/ directory as all future tests for other qemu subsystems, so
>> we could probably share quite some of the framework code. (We were
>> initially talking about image streaming tests, which need a real VM
>> instead of just qemu-img/io and some monitor interaction - it's easy to
>> imagine similar cases)
>>
>> What do you think?
> 
> I'm fine with doing that. 

Anthony, how would we merge this best?

I can rewrite the history of qemu-iotests to move everything into a
tests/qemu-iotests/ directory and rewrite the subject lines of all
commits to include "qemu-iotests" (actually I have just tried it out
locally, so this part is done). We could then just pull from this
temporary repository and keep all of the existing git history.

I would send a pull request then without reposting all the patches in
the history of qemu-iotests as some of them are pretty big.

Would that work for you? Should I add a Signed-off-by to each patch for
rewriting the history or would it be okay with Christoph's existing SoB?

Kevin

  reply	other threads:[~2012-02-20 16:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-16 15:01 [Qemu-devel] Merging qemu-iotests into qemu.git? Kevin Wolf
2012-02-16 20:53 ` Christoph Hellwig
2012-02-20 16:42   ` Kevin Wolf [this message]
2012-02-22 14:34     ` Anthony Liguori

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=4F4277F1.4080109@redhat.com \
    --to=kwolf@redhat.com \
    --cc=Qemu-devel@nongnu.org \
    --cc=anthony@codemonkey.ws \
    --cc=hch@lst.de \
    --cc=stefanha@linux.vnet.ibm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.