From: Kevin Wolf <kwolf@redhat.com>
To: Corentin Chary <corentin.chary@gmail.com>
Cc: qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH] vnc: split encoding in specific files
Date: Wed, 02 Jun 2010 12:17:33 +0200 [thread overview]
Message-ID: <4C062FBD.2010701@redhat.com> (raw)
In-Reply-To: <AANLkTillJyQk1VGCkok8hmOA21FnzFPf_G0pwhAq_sys@mail.gmail.com>
Am 02.06.2010 12:06, schrieb Corentin Chary:
> On Tue, May 4, 2010 at 10:12 AM, Kevin Wolf <kwolf@redhat.com> wrote:
>> Am 03.05.2010 19:15, schrieb Anthony Liguori:
>>> On 05/03/2010 07:31 AM, Corentin Chary wrote:
>>>> This will allow to implement new encodings (tight, zrle, ..)
>>>> in a cleaner way. This may hurt performances, because some
>>>> functions like vnc_convert_pixel are not static anymore, but
>>>> should not be a problem with gcc 4.5 and the new -flto.
>>>>
>>>> Signed-off-by: Corentin Chary<corentincj@iksaif.net>
>>>>
>>>
>>> Applied. Thanks.
>>>
>>> It's probably time to make a vnc directory too.
>>
>> Or maybe one for all of the interfaces we currently have in the root
>> directory? So it would include not only VNC, but also SDL and curses.
>>
>> Kevin
>>
>
>
> vnc-encodnig-tight.c is growing up, and I think I'll split it, again.
> So, maybe it's time to move VNC code (and others) to a subdirectory.
>
> I suggest ui/ .
> If it's ok, I'll make the patch.
ui/ sounds good.
Kevin
prev parent reply other threads:[~2010-06-02 10:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 12:31 [Qemu-devel] [PATCH] vnc: split encoding in specific files Corentin Chary
2010-05-03 15:26 ` [Qemu-devel] " Anthony Liguori
2010-05-03 17:15 ` [Qemu-devel] " Anthony Liguori
2010-05-04 8:12 ` Kevin Wolf
2010-05-04 14:26 ` Anthony Liguori
2010-06-02 10:06 ` Corentin Chary
2010-06-02 10:17 ` Kevin Wolf [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=4C062FBD.2010701@redhat.com \
--to=kwolf@redhat.com \
--cc=agraf@suse.de \
--cc=corentin.chary@gmail.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).