kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm-devel <kvm@vger.kernel.org>
Subject: Re: extboot.bin required in git
Date: Wed, 02 Sep 2009 19:20:30 +0300	[thread overview]
Message-ID: <4A9E9B4E.3030401@redhat.com> (raw)
In-Reply-To: <4A9E9AB6.8080905@siemens.com>

On 09/02/2009 07:17 PM, Jan Kiszka wrote:
>> IIRC it works in master somehow.
>>
>>      
> Old extboot.bin still hanging around in your pc-bios folder...? :)
>
>    

I'm sure I deleted them... but can't argue with reality.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2009-09-02 16:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-02 14:34 extboot.bin required in git Jan Kiszka
2009-09-02 14:38 ` Avi Kivity
2009-09-02 14:51   ` Jan Kiszka
2009-09-02 15:20     ` Avi Kivity
2009-09-02 15:26       ` Jan Kiszka
2009-09-02 15:31         ` Jan Kiszka
2009-09-02 15:40           ` Avi Kivity
2009-09-02 16:17             ` Jan Kiszka
2009-09-02 16:20               ` Avi Kivity [this message]
2009-09-02 15:40         ` Avi Kivity

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=4A9E9B4E.3030401@redhat.com \
    --to=avi@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.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 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).