From: Blue Swirl <blauwirbel@gmail.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4 00/10] initial spice support.
Date: Mon, 30 Aug 2010 18:58:01 +0000 [thread overview]
Message-ID: <AANLkTikJbOaE-8q_NcX9Z60t2ssGCasnqm4dj-c5OVkb@mail.gmail.com> (raw)
In-Reply-To: <4C7B705E.60404@redhat.com>
On Mon, Aug 30, 2010 at 8:48 AM, Gerd Hoffmann <kraxel@redhat.com> wrote:
> On 08/28/10 08:42, Blue Swirl wrote:
>>
>> On Fri, Aug 27, 2010 at 9:59 AM, Gerd Hoffmann<kraxel@redhat.com> wrote:
>>>
>>> Hi,
>>>
>>> Here comes v4 of the iniial spice support patch series, hopefully the
>>> final version. It brings just the very basic bits:
>>>
>>> * Detect spice in configure, Makefile windup.
>>> * Support for keyboard, mouse and tablet.
>>> * Support for simple display output (works as DisplayChangeListener,
>>> plays with any gfx card, sends simple draw commands to update
>>> dirty regions).
>>>
>>> Note that this patch series does *not* yet contain the qxl paravirtual
>>> gfx card. That will come as part of a additional patch series after
>>> sorting the vgabios support.
>>>
>>> The patches are also available in the git repository at:
>>> git://anongit.freedesktop.org/spice/qemu submit.4
>>
>> Please read CODING_STYLE, especially the braces rule.
>
> I'm aware of the coding style.
Wilful misconduct? May I ask if there are other things that you don't
agree with and you are covertly working against?
> I'm also aware of the recent
> flam^Wdiscussions on that topic, especially the braces rule. I didn't read
> the whole thread though. Is there some result? If so, can someone
> summarize please?
There was no conclusion. One point that was raised is that
reformatting of existing code was seen problematic. That would mean
that if offending code is let in, it will never be fixed.
next prev parent reply other threads:[~2010-08-30 18:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-27 9:59 [Qemu-devel] [PATCH v4 00/10] initial spice support Gerd Hoffmann
2010-08-27 9:59 ` [Qemu-devel] [PATCH v4 01/10] Use display types for local display only Gerd Hoffmann
2010-08-27 9:59 ` [Qemu-devel] [PATCH v4 02/10] Use machine_init() to register virtfs config options Gerd Hoffmann
2010-08-27 9:59 ` [Qemu-devel] [PATCH v4 03/10] add pflib: PixelFormat conversion library Gerd Hoffmann
2010-08-27 9:59 ` [Qemu-devel] [PATCH v4 04/10] configure: add logging Gerd Hoffmann
2010-08-27 9:59 ` [Qemu-devel] [PATCH v4 05/10] add spice into the configure file Gerd Hoffmann
2010-08-27 9:59 ` [Qemu-devel] [PATCH v4 06/10] spice: core bits Gerd Hoffmann
2010-08-27 9:59 ` [Qemu-devel] [PATCH v4 07/10] spice: add keyboard Gerd Hoffmann
2010-08-27 9:59 ` [Qemu-devel] [PATCH v4 08/10] spice: add mouse Gerd Hoffmann
2010-08-27 9:59 ` [Qemu-devel] [PATCH v4 09/10] spice: simple display Gerd Hoffmann
2010-08-27 12:42 ` Anthony Liguori
2010-08-27 9:59 ` [Qemu-devel] [PATCH v4 10/10] spice: add tablet support Gerd Hoffmann
2010-08-28 6:42 ` [Qemu-devel] [PATCH v4 00/10] initial spice support Blue Swirl
2010-08-30 8:48 ` Gerd Hoffmann
2010-08-30 18:58 ` Blue Swirl [this message]
2010-08-30 19:02 ` Anthony Liguori
2010-08-30 19:32 ` Gerd Hoffmann
2010-08-30 19:45 ` Blue Swirl
2010-08-31 9:54 ` Gerd Hoffmann
2010-08-31 13:09 ` Anthony Liguori
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=AANLkTikJbOaE-8q_NcX9Z60t2ssGCasnqm4dj-c5OVkb@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=kraxel@redhat.com \
--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).