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 331CF200C08 for ; Thu, 26 Jan 2017 14:29:46 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 31CB7160B4C; Thu, 26 Jan 2017 13:29:46 +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 72F35160B40 for ; Thu, 26 Jan 2017 14:29:45 +0100 (CET) Received: (qmail 22203 invoked by uid 500); 26 Jan 2017 13:29:43 -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 22187 invoked by uid 99); 26 Jan 2017 13:29:42 -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; Thu, 26 Jan 2017 13:29:42 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 85AABDFB0E; Thu, 26 Jan 2017 13:29:40 +0000 (UTC) From: drigodwin To: dev@brooklyn.apache.org Reply-To: dev@brooklyn.apache.org References: In-Reply-To: Subject: [GitHub] brooklyn-docs issue #143: Update disk usage explanation Content-Type: text/plain Message-Id: <20170126132940.85AABDFB0E@git1-us-west.apache.org> Date: Thu, 26 Jan 2017 13:29:40 +0000 (UTC) archived-at: Thu, 26 Jan 2017 13:29:46 -0000 Github user drigodwin commented on the issue: https://github.com/apache/brooklyn-docs/pull/143 This change is only true for the Karaf distibution of Apache Brooklyn. This is not the default so I would suggest holding off merging this PR until it is. --- 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. ---