From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Libvirt and spice [3]
Date: Tue, 29 Mar 2016 21:57:11 +0100 [thread overview]
Message-ID: <1459285031.30749.224.camel@ipfire.org> (raw)
In-Reply-To: <1459284991.30749.223.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 580 bytes --]
I made some minor modifications in the following commits. Please have a look and
take this into account in the future.
On Tue, 2016-03-29 at 21:56 +0100, Michael Tremer wrote:
> Hi,
>
> all merged. Thanks.
>
> -Michael
>
> On Tue, 2016-03-29 at 20:57 +0200, Jonatan Schlag wrote:
> >
> > Hi,
> > this is the third patch series for spice.
> > The only difference between this series and the previous one ist that the
> > rootfiles of all build dependencies are moved into config/rootfiles/common.
> > Everything should build now.
> >
> > Regards Jonatan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-03-29 20:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 18:57 Jonatan Schlag
2016-03-29 18:57 ` [PATCH 1/7] New package opus (required by spice) Jonatan Schlag
2016-03-29 18:57 ` [PATCH 2/7] New package python-six (required by spice (only for build)) Jonatan Schlag
2016-03-29 18:57 ` [PATCH 3/7] New package python-pyparsing " Jonatan Schlag
2016-03-29 18:57 ` [PATCH 4/7] New package spice-protocol " Jonatan Schlag
2016-03-29 18:57 ` [PATCH 5/7] New package spice Jonatan Schlag
2016-03-29 18:57 ` [PATCH 6/7] Add all new packages (opus, python-pyparsing, python-six, spice-protocol, spice) to make.sh Jonatan Schlag
2016-03-29 18:57 ` [PATCH 7/7] Enable spice support in qemu, add spice as a dependency for qemu and bump qemu version number Jonatan Schlag
2016-03-29 20:56 ` Libvirt and spice [3] Michael Tremer
2016-03-29 20:57 ` Michael Tremer [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=1459285031.30749.224.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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