restructure results

1 files changed, 0 insertions, 110 deletions

diff --git a/results/classifier/118/all/1038136 b/results/classifier/118/all/1038136
deleted file mode 100644
index 0779c8c2..00000000
--- a/results/classifier/118/all/1038136
+++ /dev/null
@@ -1,110 +0,0 @@
-debug: 0.987
-architecture: 0.981
-PID: 0.979
-permissions: 0.978
-device: 0.977
-register: 0.976
-assembly: 0.974
-peripherals: 0.973
-arm: 0.973
-performance: 0.967
-risc-v: 0.963
-semantic: 0.960
-boot: 0.959
-network: 0.952
-socket: 0.950
-mistranslation: 0.942
-KVM: 0.934
-vnc: 0.934
-user-level: 0.934
-ppc: 0.932
-VMM: 0.932
-files: 0.930
-virtual: 0.930
-graphic: 0.925
-kernel: 0.925
-TCG: 0.921
-hypervisor: 0.910
-i386: 0.772
-x86: 0.744
-
-lack of keycode 89 for br-abnt2 keyboards
-
-qemu-kvm-1.1.1
-host system: slackware64-13.37
-Bug detailed description:
-Independent of Guest OS nothing happens when keycode 89 is pressed. 
-If you select option "-k pt-br" at qemu commandline you get keycode 89 but there is no more keycode 26 (dead_acute dead_grave) and keycode 51 fails on "less" sign.
-If you have a numeric keyboard you can use its "slash" key but there is no means to use the question mark, causing discomfort when you are scripting or programming.
-
-I have the exact same problem.
-
-
-Bug is confirmed and at least one and a half year old, according to this blog post, with a hack for solving it:
-http://blog.nielshorn.net/2011/03/qemu-and-brazilian-keyboards/
-
-I've managed to resolve it applying the following patch (without "-k pt-br"):
-
---- qemu-1.6.0+dfsg.orig/ui/x_keymap.c
-+++ qemu-1.6.0+dfsg/ui/x_keymap.c
-@@ -94,7 +94,7 @@ static const uint8_t x_keycode_to_pc_key
-  */
-
- static const uint8_t evdev_keycode_to_pc_keycode[61] = {
--    0,         /*  97 EVDEV - RO   ("Internet" Keyboards) */
-+    0x73,      /*  97 EVDEV - /?°  (ABNT2 Keyboards) */
-     0,         /*  98 EVDEV - KATA (Katakana) */
-     0,         /*  99 EVDEV - HIRA (Hiragana) */
-     0x79,      /* 100 EVDEV - HENK (Henkan) */
-
-
-Attached patch (may not apply cleanly as I edited it manually to correct for space alignment; but c'mon, it is so straight forward).
-
-Thanks
-I will test it
-Gilcio
-
-Em 27/11/2013, às 07:25, rslemos <email address hidden> escreveu:
-
-> I've managed to resolve it applying the following patch (without "-k pt-
-> br"):
->
-> --- qemu-1.6.0+dfsg.orig/ui/x_keymap.c
-> +++ qemu-1.6.0+dfsg/ui/x_keymap.c
-> @@ -94,7 +94,7 @@ static const uint8_t x_keycode_to_pc_key
->  */
->
-> static const uint8_t evdev_keycode_to_pc_keycode[61] = {
-> -    0,         /*  97 EVDEV - RO   ("Internet" Keyboards) */
-> +    0x73,      /*  97 EVDEV - /?°  (ABNT2 Keyboards) */
->     0,         /*  98 EVDEV - KATA (Katakana) */
->     0,         /*  99 EVDEV - HIRA (Hiragana) */
->     0x79,      /* 100 EVDEV - HENK (Henkan) */
->
-> --
-> You received this bug notification because you are subscribed to the bug
-> report.
-> https://bugs.launchpad.net/bugs/1038136
->
-> Title:
->  lack of keycode 89 for br-abnt2 keyboards
->
-> Status in QEMU:
->  Confirmed
->
-> Bug description:
->  qemu-kvm-1.1.1
->  host system: slackware64-13.37
->  Bug detailed description:
->  Independent of Guest OS nothing happens when keycode 89 is pressed.
->  If you select option "-k pt-br" at qemu commandline you get keycode 89 but there is no more keycode 26 (dead_acute dead_grave) and keycode 51 fails on "less" sign.
->  If you have a numeric keyboard you can use its "slash" key but there is no means to use the question mark, causing discomfort when you are scripting or programming.
->
-> To manage notifications about this bug go to:
-> https://bugs.launchpad.net/qemu/+bug/1038136/+subscriptions
-
-
-Looks like this the key has been added by this commit here:
-http://git.qemu.org/?p=qemu.git;a=commitdiff;h=33aa30cafcce053b83
-So I think we can close this bug ticket now.
-