From: Remote Duck <duck@sophos.com.au>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Using "invisible wall" patch to produce 0.8.2?
Date: Thu, 15 Jun 2006 22:04:26 -0000 [thread overview]
Message-ID: <Pine.WNT.4.64.0606160752020.2884@med> (raw)
Following recent discussion of the "invisible wall" patch...would the
developers consider quickly releasing a 0.8.2 version which contained
only this change from 0.8.1?
I can't help but think that many potential new adopters of QEMU might be
put off for ever by this problem -- as Julian Seward pointed out, QEMU is
effectively unusable without the patch, but seems to work perfectly well
once it is applied.
Call it a "customer-facing improvement" :-)
(I didn't realise just how often one needs to sweep the mouse to the edge
or into a corner of the screen when using Windows, though it stands to
reason when you think where the [Start] menu is, and where the principal
window controls are when a program is maximised. It does give an entirely
false but bad impression of the rest of QEMU that this important activity
seems to be impossible.)
next reply other threads:[~2006-06-15 22:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-15 22:04 Remote Duck [this message]
2006-08-20 23:18 ` [Qemu-devel] Using "invisible wall" patch to produce 0.8.2? Aurelien Jarno
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=Pine.WNT.4.64.0606160752020.2884@med \
--to=duck@sophos.com.au \
--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).