From: Avi Kivity <avi@redhat.com>
To: Daniel Gollub <gollub@b1-systems.de>
Cc: kvm@vger.kernel.org
Subject: Re: Fwd: buildbot failure in qemu-kvm on disable_kvm_i386_centos_5_2
Date: Mon, 27 Jul 2009 12:21:06 +0300 [thread overview]
Message-ID: <4A6D7182.4030608@redhat.com> (raw)
In-Reply-To: <200907261414.14245.gollub@b1-systems.de>
On 07/26/2009 03:14 PM, Daniel Gollub wrote:
> Hi Avi,
>
> On Sunday 26 July 2009 02:01:18 pm Avi Kivity wrote:
> [...]
>
>> Can you set up testing for the 'next' branch? It will catch issues much
>> earlier.
>>
>
> Actutally i thought it is. But for some reason it is not getting notified by
> the git hook. Could you ping me on IRC before you push something (only) to
> next-branch, so i can have a look at the buildbot logs ...
>
That was broken at my end; fixed.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2009-07-27 9:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-26 11:51 Fwd: buildbot failure in qemu-kvm on disable_kvm_i386_centos_5_2 Daniel Gollub
2009-07-26 12:01 ` Avi Kivity
2009-07-26 12:14 ` Daniel Gollub
2009-07-27 9:21 ` Avi Kivity [this message]
2009-07-27 9:35 ` Daniel Gollub
2009-07-27 10:15 ` Avi Kivity
2009-07-26 12:19 ` Avi Kivity
2009-07-26 12:17 ` Daniel Gollub
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=4A6D7182.4030608@redhat.com \
--to=avi@redhat.com \
--cc=gollub@b1-systems.de \
--cc=kvm@vger.kernel.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 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.