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 EB21E200BF8 for ; Fri, 13 Jan 2017 23:49:00 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id E9C91160B3F; Fri, 13 Jan 2017 22:49:00 +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 380F5160B2E for ; Fri, 13 Jan 2017 23:49:00 +0100 (CET) Received: (qmail 75420 invoked by uid 500); 13 Jan 2017 22:48:59 -0000 Mailing-List: contact dev-help@zookeeper.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@zookeeper.apache.org Delivered-To: mailing list dev@zookeeper.apache.org Received: (qmail 75409 invoked by uid 99); 13 Jan 2017 22:48:59 -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, 13 Jan 2017 22:48:59 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 0140BDFC16; Fri, 13 Jan 2017 22:48:59 +0000 (UTC) From: hanm To: dev@zookeeper.apache.org Reply-To: dev@zookeeper.apache.org References: In-Reply-To: Subject: [GitHub] zookeeper issue #120: ZOOKEEPER-261 Content-Type: text/plain Message-Id: <20170113224859.0140BDFC16@git1-us-west.apache.org> Date: Fri, 13 Jan 2017 22:48:59 +0000 (UTC) archived-at: Fri, 13 Jan 2017 22:49:01 -0000 Github user hanm commented on the issue: https://github.com/apache/zookeeper/pull/120 Right, it is committed, confirmed. I was only checking the apache mirror on git (https://github.com/apache/zookeeper), instead of the apache git directly. I suspect there is some infra issues on Apache (the JIRA was done yesterday) which contributes to the bridging between various systems not working as expected, leading to this PR not closed automatically. --- 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. ---