On Fri, Aug 14, 2015 at 03:51:03PM +0100, Peter Maydell wrote: > On 14 August 2015 at 14:57, Jeff Cody <jc...@redhat.com> wrote: > > The following changes since commit be1f13ac9d9fc21908975460652a72f5f0c018c5: > > > > Merge remote-tracking branch 'remotes/lalrae/tags/mips-20150813' into > > staging (2015-08-13 17:47:44 +0100) > > > > are available in the git repository at: > > > > > > g...@github.com:codyprime/qemu-kvm-jtc.git tags/block-pull-request > > > > for you to fetch changes up to e424aff5f307227b1c2512bbb8ece891bb895cef: > > > > mirror: Fix coroutine reentrance (2015-08-14 09:51:31 -0400) > > > > ---------------------------------------------------------------- > > Block job patches > > ---------------------------------------------------------------- > > > > Kevin Wolf (1): > > mirror: Fix coroutine reentrance > > > > Stefan Hajnoczi (1): > > block/mirror: limit qiov to IOV_MAX elements > > Your pull req tag has not only these two commits in it, > but also a merge commit ("Merge branch 'block-next' into HEAD). > Why is that? > > thanks > -- PMM
Hi, I was trying to keep a commit id stable (for 'block/mirror: limit qiov to IOV_MAX elements'), so it could be used for a downstream backport before this patch actually hit the official upstream repo. Does this cause you any issues (i.e., should I rebase and submit a new pull request)? Thanks, Jeff