Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 95356200CAD for ; Wed, 28 Jun 2017 23:58:52 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 93C98160BF7; Wed, 28 Jun 2017 21:58:52 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id D1CAC160BD9 for ; Wed, 28 Jun 2017 23:58:51 +0200 (CEST) Received: (qmail 60692 invoked by uid 500); 28 Jun 2017 21:58:51 -0000 Mailing-List: contact dev-help@brooklyn.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@brooklyn.apache.org Delivered-To: mailing list dev@brooklyn.apache.org Received: (qmail 60681 invoked by uid 99); 28 Jun 2017 21:58:50 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Jun 2017 21:58:50 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id AAA70DFB0D; Wed, 28 Jun 2017 21:58:50 +0000 (UTC) From: aledsage To: dev@brooklyn.apache.org Reply-To: dev@brooklyn.apache.org References: In-Reply-To: Subject: [GitHub] brooklyn-server issue #731: BROOKLYN-440: ssh not use StreamGobbler for logg... Content-Type: text/plain Message-Id: <20170628215850.AAA70DFB0D@git1-us-west.apache.org> Date: Wed, 28 Jun 2017 21:58:50 +0000 (UTC) archived-at: Wed, 28 Jun 2017 21:58:52 -0000 Github user aledsage commented on the issue: https://github.com/apache/brooklyn-server/pull/731 @neykov @geomacy thanks for comments - I've added another commit to address those. Could you review again please? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---