From: Avi Kivity <avi@redhat.com>
To: "Kevin O'Connor" <kevin@koconnor.net>
Cc: KVM list <kvm@vger.kernel.org>,
seabios@seabios.org, qemu-devel <qemu-devel@nongnu.org>,
"Justin M. Forbes" <jforbes@redhat.com>,
Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [SeaBIOS] [PATCH] mark irq9 active high in DSDT
Date: Wed, 27 Oct 2010 15:27:58 +0200 [thread overview]
Message-ID: <4CC828DE.9050908@redhat.com> (raw)
In-Reply-To: <4CC56188.1090702@redhat.com>
On 10/25/2010 12:52 PM, Avi Kivity wrote:
>> I'm okay with making tags and branches of seabios for bug fixes. So
>> far qemu/kvm has just grabbed various builds of seabios - is it
>> worthwhile to branch off of the seabios-0.6.1 version - which would
>> mean qemu/kvm would pull in additional changes beyond the bug fix
>> above?
>
>
> qemu 0.12 is based on 0.5.1-stable, appears to be an untagged commit
> qemu 0.13 is based on 17d3e46511, doesn't appear to be a part of a
> branch or a tag?
>
> git-wise, tags are more important than branches. You can always
> retrofit a branch to a tag (and you can always retrofit a tag to a
> commit hash). For the qemu git repositories, neither matter so much
> since the commit is recorded in git; but the distro people really like
> nice stable tags with lots of digits and dots in them.
>
On the last kvm conf call Anthony said that he'll be happy to include an
updated seabios with qemu 0.13.1, so a new release would be appreciated.
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Kevin O'Connor <kevin@koconnor.net>
Cc: "Justin M. Forbes" <jforbes@redhat.com>,
seabios@seabios.org, qemu-devel <qemu-devel@nongnu.org>,
KVM list <kvm@vger.kernel.org>
Subject: [Qemu-devel] Re: [SeaBIOS] [PATCH] mark irq9 active high in DSDT
Date: Wed, 27 Oct 2010 15:27:58 +0200 [thread overview]
Message-ID: <4CC828DE.9050908@redhat.com> (raw)
In-Reply-To: <4CC56188.1090702@redhat.com>
On 10/25/2010 12:52 PM, Avi Kivity wrote:
>> I'm okay with making tags and branches of seabios for bug fixes. So
>> far qemu/kvm has just grabbed various builds of seabios - is it
>> worthwhile to branch off of the seabios-0.6.1 version - which would
>> mean qemu/kvm would pull in additional changes beyond the bug fix
>> above?
>
>
> qemu 0.12 is based on 0.5.1-stable, appears to be an untagged commit
> qemu 0.13 is based on 17d3e46511, doesn't appear to be a part of a
> branch or a tag?
>
> git-wise, tags are more important than branches. You can always
> retrofit a branch to a tag (and you can always retrofit a tag to a
> commit hash). For the qemu git repositories, neither matter so much
> since the commit is recorded in git; but the distro people really like
> nice stable tags with lots of digits and dots in them.
>
On the last kvm conf call Anthony said that he'll be happy to include an
updated seabios with qemu 0.13.1, so a new release would be appreciated.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-10-27 13:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20101020093441.GP10207@redhat.com>
[not found] ` <20101021020020.GA21095@morn.localdomain>
2010-10-21 10:07 ` [SeaBIOS] [PATCH] mark irq9 active high in DSDT Avi Kivity
2010-10-21 10:07 ` [Qemu-devel] " Avi Kivity
2010-10-23 14:12 ` Kevin O'Connor
2010-10-23 14:12 ` [Qemu-devel] " Kevin O'Connor
2010-10-25 10:52 ` Avi Kivity
2010-10-25 10:52 ` [Qemu-devel] " Avi Kivity
2010-10-27 13:27 ` Avi Kivity [this message]
2010-10-27 13:27 ` Avi Kivity
2010-10-31 22:46 ` Kevin O'Connor
2010-10-31 22:46 ` [Qemu-devel] " Kevin O'Connor
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=4CC828DE.9050908@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=jforbes@redhat.com \
--cc=kevin@koconnor.net \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.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.