From: Dustin Kirkland <kirkland@canonical.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm-devel <kvm@vger.kernel.org>, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [ANNOUNCE] qemu-kvm-0.12.0-rc2 released
Date: Sun, 20 Dec 2009 21:39:30 -0600 [thread overview]
Message-ID: <d9c105ea0912201939u3fb29d7fs7d25b22263a2e7fa@mail.gmail.com> (raw)
In-Reply-To: <4B2E5017.5000500@redhat.com>
On Sun, Dec 20, 2009 at 10:25 AM, Avi Kivity <avi@redhat.com> wrote:
> On 12/15/2009 05:21 PM, Dustin Kirkland wrote:
>>
>>> - fetch the submodules and include them in the tarball
>>>
>>
>> ...
>>
>> I think this option would help keep us all on the same page. But I
>> could live with pointers to the submodules, since packaging a new
>> release only happens a couple of times per year.
>>
>>
>
> Due to time constraints I went for the simpler option of adding a generated
> EXTERNAL_DEPENDENCIES file. Patches for including the source are welcome.
Fair enough. It's straightforward by hand, and I only really package
twice a year.
What about the qemu-system-arm build break I also mentioned? That's
currently blocking my packaging.
Thanks,
:-Dustin
next prev parent reply other threads:[~2009-12-21 3:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4B2684EC.2040504@redhat.com>
2009-12-14 21:58 ` [Qemu-devel] Re: [ANNOUNCE] qemu-kvm-0.12.0-rc2 released Dustin Kirkland
2009-12-15 9:10 ` Avi Kivity
2009-12-15 14:23 ` Lennart Sorensen
2009-12-15 14:29 ` Anthony Liguori
2009-12-15 15:21 ` Dustin Kirkland
2009-12-18 4:51 ` Dustin Kirkland
2009-12-20 16:25 ` Avi Kivity
2009-12-21 3:39 ` Dustin Kirkland [this message]
2009-12-21 9:30 ` Avi Kivity
[not found] ` <4B2748B6.9080305@eseco.de>
2009-12-15 9:07 ` Avi Kivity
2009-12-15 14:31 ` Anthony Liguori
2009-12-15 14:41 ` Gerd Hoffmann
2009-12-15 18:22 ` Luiz Capitulino
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=d9c105ea0912201939u3fb29d7fs7d25b22263a2e7fa@mail.gmail.com \
--to=kirkland@canonical.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).