SSH: Streamline SshRemoteProcessRunner's output handling.

Make it just like SshRemoteProcess (and QProcess). The current
implementation annoyingly forces client code to establish additional
signal/slot connections, even if they only want to evaluate the output
at the end.

Change-Id: Id8c30dd156574d7d26d848d8e0705856a16d3747
Reviewed-by: hjk <qthjk@ovi.com>

1 files changed, 2 insertions, 2 deletions

diff --git a/tests/manual/ssh/remoteprocess/remoteprocesstest.h b/tests/manual/ssh/remoteprocess/remoteprocesstest.h
index 73dd633e1a..3aef059272 100644
--- a/tests/manual/ssh/remoteprocess/remoteprocesstest.h
+++ b/tests/manual/ssh/remoteprocess/remoteprocesstest.h
@@ -51,8 +51,8 @@ public:
 private slots:
     void handleConnectionError();
     void handleProcessStarted();
-    void handleProcessStdout(const QByteArray &output);
-    void handleProcessStderr(const QByteArray &output);
+    void handleProcessStdout();
+    void handleProcessStderr();
     void handleProcessClosed(int exitStatus);
     void handleTimeout();
     void handleReadyRead();