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 1BD3C200C3A for ; Fri, 3 Mar 2017 04:08:21 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 1A677160B7A; Fri, 3 Mar 2017 03:08:21 +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 5A95B160B6F for ; Fri, 3 Mar 2017 04:08:20 +0100 (CET) Received: (qmail 93729 invoked by uid 500); 3 Mar 2017 03:08:19 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 93718 invoked by uid 99); 3 Mar 2017 03:08:18 -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; Fri, 03 Mar 2017 03:08:18 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id A47D6DFC15; Fri, 3 Mar 2017 03:08:18 +0000 (UTC) From: dmabry To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack issue #1974: CLOUDSTACK-9795: moved logrotate from cron.daily to ... Content-Type: text/plain Message-Id: <20170303030818.A47D6DFC15@git1-us-west.apache.org> Date: Fri, 3 Mar 2017 03:08:18 +0000 (UTC) archived-at: Fri, 03 Mar 2017 03:08:21 -0000 Github user dmabry commented on the issue: https://github.com/apache/cloudstack/pull/1974 shall I close this PR or do you guys need it open to make sure the cherry-pick happens? --- 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. ---