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 396AD200B57 for ; Sat, 2 Jul 2016 00:16:17 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 36A42160A61; Fri, 1 Jul 2016 22:16:17 +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 7EB8C160A6C for ; Sat, 2 Jul 2016 00:16:16 +0200 (CEST) Received: (qmail 85517 invoked by uid 500); 1 Jul 2016 22:16:15 -0000 Mailing-List: contact dev-help@trafficserver.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@trafficserver.apache.org Delivered-To: mailing list dev@trafficserver.apache.org Received: (qmail 85451 invoked by uid 99); 1 Jul 2016 22:16:15 -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, 01 Jul 2016 22:16:15 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 1D635E009D; Fri, 1 Jul 2016 22:16:15 +0000 (UTC) From: zwoop To: dev@trafficserver.apache.org Reply-To: dev@trafficserver.apache.org References: In-Reply-To: Subject: [GitHub] trafficserver issue #782: TS-4633: Fix an erroneous warning message when rea... Content-Type: text/plain Message-Id: <20160701221615.1D635E009D@git1-us-west.apache.org> Date: Fri, 1 Jul 2016 22:16:15 +0000 (UTC) archived-at: Fri, 01 Jul 2016 22:16:17 -0000 Github user zwoop commented on the issue: https://github.com/apache/trafficserver/pull/782 :+1: Lets back port this to 6.2.0 as well, since we have to re-roll because of the other fix. --- 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. ---