Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-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 04EED10CE0 for ; Tue, 19 May 2015 19:46:34 +0000 (UTC) Received: (qmail 34224 invoked by uid 500); 19 May 2015 19:46:33 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 34169 invoked by uid 500); 19 May 2015 19:46:33 -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 34158 invoked by uid 99); 19 May 2015 19:46:33 -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; Tue, 19 May 2015 19:46:33 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 3E2FAE2F6E; Tue, 19 May 2015 19:46:33 +0000 (UTC) From: isoutham To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack pull request: Pep8 and some unit tests Content-Type: text/plain Message-Id: <20150519194633.3E2FAE2F6E@git1-us-west.apache.org> Date: Tue, 19 May 2015 19:46:33 +0000 (UTC) Github user isoutham commented on the pull request: https://github.com/apache/cloudstack/pull/265#issuecomment-103648791 It looks like I have somehow managed to put the second PR in the first (was a seperate branch) not quite sure what I did here. Ignore the first and treat it as one I would say but if you feel otherwise, let me know. On 19 May 2015 at 21:20, Wilder Rodrigues wrote: > It seems this PR came with the same commit as the previous one, that's why > Travis is now building the #262 > again. > > Did you create a second PR with the same commit + extra fixes? Should we > just ignore the previous one? > > — > Reply to this email directly or view it on GitHub > . > --- 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. ---