Return-Path: X-Original-To: apmail-cordova-dev-archive@www.apache.org Delivered-To: apmail-cordova-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3991D11116 for ; Tue, 15 Jul 2014 03:14:46 +0000 (UTC) Received: (qmail 16683 invoked by uid 500); 15 Jul 2014 03:14:45 -0000 Delivered-To: apmail-cordova-dev-archive@cordova.apache.org Received: (qmail 16603 invoked by uid 500); 15 Jul 2014 03:14:45 -0000 Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cordova.apache.org Delivered-To: mailing list dev@cordova.apache.org Received: (qmail 16592 invoked by uid 99); 15 Jul 2014 03:14:45 -0000 Received: from tyr.zones.apache.org (HELO tyr.zones.apache.org) (140.211.11.114) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Jul 2014 03:14:45 +0000 Received: by tyr.zones.apache.org (Postfix, from userid 65534) id 6EA7B94B7CD; Tue, 15 Jul 2014 03:14:44 +0000 (UTC) From: clelland To: dev@cordova.apache.org Reply-To: dev@cordova.apache.org References: In-Reply-To: Subject: [GitHub] cordova-plugin-file pull request: CB-7093 Ported automated File te... Content-Type: text/plain Message-Id: <20140715031444.6EA7B94B7CD@tyr.zones.apache.org> Date: Tue, 15 Jul 2014 03:14:44 +0000 (UTC) Github user clelland commented on the pull request: https://github.com/apache/cordova-plugin-file/pull/60#issuecomment-48985942 Yeah, the URL/URI messages have been there a long time; I just figured I'd take the opportunity to clean them up now, especially as the console log is much more in-your-face with the new test runner. I didn't see the earlier discussion re: plugin.xml on the other PR; I'll try to get that sorted out before the next plugin release, though. Thanks. --- 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. ---