1 files changed, 41 insertions, 0 deletions
diff --git a/results/classifier/111/review/1612908 b/results/classifier/111/review/1612908
new file mode 100644
index 00000000..f0b49d73
--- /dev/null
+++ b/results/classifier/111/review/1612908
@@ -0,0 +1,41 @@
+semantic: 0.150
+socket: 0.149
+other: 0.114
+device: 0.107
+network: 0.097
+graphic: 0.076
+performance: 0.051
+vnc: 0.043
+files: 0.040
+permissions: 0.039
+debug: 0.038
+PID: 0.038
+boot: 0.034
+KVM: 0.024
+network: 0.256
+debug: 0.200
+other: 0.107
+socket: 0.097
+files: 0.079
+PID: 0.047
+semantic: 0.043
+device: 0.039
+performance: 0.029
+boot: 0.027
+vnc: 0.024
+permissions: 0.020
+KVM: 0.017
+graphic: 0.015
+
+qom-[list,tree,get,set] don't accept tcp endpoint arg
+
+Hi, 
+
+I'm using origin/master [6bbbb0ac13...]. When I run any of the commands in 'qemu/scripts/qmp/qom-[list,tree,get,set]', the help text says that it can connect to a QEMU instance by passing either a path to a unix socket or a tcp endpoint in the format "host:port". The unix socket variant works but the tcp endpoint variant does not. QEMUMonitorProtocol accepts either a string (unix socket) or a tuple (host,port). None of the qom-* scripts actually massage the '-s' argument into a tuple. 
+
+I have a patch to fix this issue that I can submit to the developer list.
+
+Hi! Triaging old bug tickets ... is this still an issue with the latest version of QEMU? If you've got a patch for this ready, please send it to the qemu-devel mailing list!
+
+[Expired for QEMU because there has been no activity for 60 days.]
+