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 8F1FB196EF for ; Thu, 7 Apr 2016 21:45:49 +0000 (UTC) Received: (qmail 10236 invoked by uid 500); 7 Apr 2016 21:45:49 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 10194 invoked by uid 500); 7 Apr 2016 21:45:49 -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 10183 invoked by uid 99); 7 Apr 2016 21:45:48 -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; Thu, 07 Apr 2016 21:45:48 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id B9A5DDFBBB; Thu, 7 Apr 2016 21:45:48 +0000 (UTC) From: swill To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack pull request: CLOUDSTACK-9305: Cloudstack Usage Breaks ... Content-Type: text/plain Message-Id: <20160407214548.B9A5DDFBBB@git1-us-west.apache.org> Date: Thu, 7 Apr 2016 21:45:48 +0000 (UTC) Github user swill commented on the pull request: https://github.com/apache/cloudstack/pull/1433#issuecomment-207101177 No one is allowed to push code to `apache/cloudstack`, you have to push it to your fork where your PR is coming from. Does that make sense? --- 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. ---