From: Gerd Hoffmann <kraxel@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Yonit Halperin <yhalperi@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/5] spice: make compression configurable.
Date: Thu, 07 Oct 2010 21:29:37 +0200 [thread overview]
Message-ID: <4CAE1FA1.9020903@redhat.com> (raw)
In-Reply-To: <AANLkTi=LnJ0dY7pEGRxdgw5YoG1KTUEh4AcmCQ5MEUOO@mail.gmail.com>
On 10/07/10 20:12, Blue Swirl wrote:
> On Thu, Oct 7, 2010 at 7:55 AM, Gerd Hoffmann<kraxel@redhat.com> wrote:
>> From: Yonit Halperin<yhalperi@redhat.com>
>>
>
> No description?
Detailed description comes here:
>> --- a/qemu-options.hx
>> +++ b/qemu-options.hx
>> @@ -704,6 +704,15 @@ The x509 file names can also be configured individually.
>> @item tls-ciphers=<list>
>> Specify which ciphers to use.
>>
>> +@item image-compression=[auto_glz|auto_lz|quic|glz|lz|off]
>> +Configure image compression (lossless).
>> +Default is auto_glz.
>> +
>> +@item jpeg-wan-compression=[auto|never|allways]
>> +@item zlib-glz-wan-compression=[auto|never|allways]
>
> 'allways' does not match what the code uses:
>
>> + [ SPICE_WAN_COMPRESSION_ALWAYS ] = "always",
Good catch, will fix.
thanks,
Gerd
next prev parent reply other threads:[~2010-10-07 19:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 7:55 [Qemu-devel] [PATCH 0/5] spice config options Gerd Hoffmann
2010-10-07 7:55 ` [Qemu-devel] [PATCH 1/5] spice: tls support Gerd Hoffmann
2010-10-07 7:55 ` [Qemu-devel] [PATCH 2/5] spice: make compression configurable Gerd Hoffmann
2010-10-07 18:12 ` Blue Swirl
2010-10-07 19:29 ` Gerd Hoffmann [this message]
2010-10-07 7:55 ` [Qemu-devel] [PATCH 3/5] spice: add config options for channel security Gerd Hoffmann
2010-10-07 18:43 ` Stefan Weil
2010-10-07 19:26 ` Gerd Hoffmann
2010-10-07 7:55 ` [Qemu-devel] [PATCH 4/5] spice: add config options for the listening address Gerd Hoffmann
2010-10-07 7:55 ` [Qemu-devel] [PATCH 5/5] spice: add misc config options Gerd Hoffmann
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=4CAE1FA1.9020903@redhat.com \
--to=kraxel@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=yhalperi@redhat.com \
/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.