From: Jonatan Schlag <jonatan.schlag@ipfire.org>
To: development@lists.ipfire.org
Subject: Spice for Libvirt
Date: Mon, 21 Mar 2016 19:47:32 +0100 [thread overview]
Message-ID: <1458586059-740-1-git-send-email-jonatan.schlag@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 392 bytes --]
This patch series contains all required packages for spice and spice itself.
Spice provides a protocol similar to vnc but is faster and support more options (audio).
I hope these patches are ok so far.
Just as a question how did the project deal with patches?
Should I wait till I get feedback for my first patches or should I send the next patches for libvirt?
Regards Jonatan
next reply other threads:[~2016-03-21 18:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 18:47 Jonatan Schlag [this message]
2016-03-21 18:47 ` [PATCH 1/7] New package opus (required by spice) Jonatan Schlag
2016-03-22 19:01 ` Michael Tremer
2016-03-21 18:47 ` [PATCH 2/7] New package python-pyparsing " Jonatan Schlag
2016-03-21 18:47 ` [PATCH 3/7] New package python-six " Jonatan Schlag
2016-03-21 18:47 ` [PATCH 4/7] New package spice-protocol " Jonatan Schlag
2016-03-21 18:47 ` [PATCH 5/7] New package spice Jonatan Schlag
2016-03-22 19:05 ` Michael Tremer
2016-03-21 18:47 ` [PATCH 6/7] Add all new packages (opus, python-pyparsing, python-six, spice-protocol, spice) to make.sh Jonatan Schlag
2016-03-22 19:07 ` Michael Tremer
2016-03-21 18:47 ` [PATCH 7/7] Enable spice support in qemu, add spice as a dependency for qemu and bump qemu version number Jonatan Schlag
2016-03-22 19:08 ` Spice for Libvirt Michael Tremer
[not found] <1458674465.28877.1@mail01.ipfire.org>
2016-03-22 21:57 ` Michael Tremer
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=1458586059-740-1-git-send-email-jonatan.schlag@ipfire.org \
--to=jonatan.schlag@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