public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: kvm-devel <kvm@vger.kernel.org>
Subject: Re: a list of small things to fix for qemu-kvm-0.12.3.1
Date: Fri, 05 Mar 2010 19:17:50 +0300	[thread overview]
Message-ID: <4B912EAE.7050108@msgid.tls.msk.ru> (raw)
In-Reply-To: <4B912D00.7020100@msgid.tls.msk.ru>

Michael Tokarev wrote:
> ..or for subsequent releases.
> 
> First of all, roms/{sea,vga}bios directories
> are empty in qemu-kvm tarballs but they're
> present in qemu tarball.  I think the sources
> for the bioses should be restored.
> 
> While at it, the EXTERNAL_DEPENDENCIES file
> should list actual git commit ID for the
> seabios used, which is "two commits ahead
> of 0.5.1 release".
> 
> And while at it, pc-bios/README should probably
> be updated to reference to roms/* as well as
> to the original sources for the binaries.  But
> that's in qemu.
> 
> The following files should be removed when
> releasing a new version:
> 
>  qemu/pc-bios/extboot.bin
>    (this one slipped in from an old directory,
>     it's now without first "qemu" component;
>    And yes, 0.12.3 tarball has that file for
>    some unknown reason).
> 
>  git-related files (.gitignore, .gitmodules
>    and kvm/.gitignore) should be removed too
>    when releasing things, IMHO.

And probably other dot-files too:

  kvm/vgabios/.cvsignore
  tests/cris/.gdbinit

And I just realized that vgabios is in kvm/vgabios as
it were in 0.11 and before.  In upstream qemu it were
moved to roms/vgabios, but see the first item in this
email above... ;)

And while at it, what about kvm/extboot/ which contains
no useful files anymore, with everything moved to
pc-bios/optionroms/ ?

> Thanks!
> 
> /mjt


      reply	other threads:[~2010-03-05 16:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-05 16:10 a list of small things to fix for qemu-kvm-0.12.3.1 Michael Tokarev
2010-03-05 16:17 ` Michael Tokarev [this message]

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=4B912EAE.7050108@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox