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 6AFD018E15 for ; Mon, 24 Aug 2015 12:08:26 +0000 (UTC) Received: (qmail 84392 invoked by uid 500); 24 Aug 2015 12:08:25 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 84333 invoked by uid 500); 24 Aug 2015 12:08:25 -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 84322 invoked by uid 99); 24 Aug 2015 12:08:25 -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; Mon, 24 Aug 2015 12:08:25 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 76097DFFA2; Mon, 24 Aug 2015 12:08:25 +0000 (UTC) From: terbolous To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack pull request: Git PR merge script improvements Content-Type: text/plain Message-Id: <20150824120825.76097DFFA2@git1-us-west.apache.org> Date: Mon, 24 Aug 2015 12:08:25 +0000 (UTC) Github user terbolous commented on the pull request: https://github.com/apache/cloudstack/pull/734#issuecomment-134167474 @remibergsma it does point to the apache repo, but with a somewhat different url I used 'git clone gh:apache/cloudstack' to initialize the repo, and that doesn't seem to include .git in the path. My url: git@github.com:apache/cloudstack Script expected url: git@github.com:apache/cloudstack.git (or using https mode) Both works, so I just wanted to give a heads up as more people might experience the same. It is true that I didn't have the apache official repo added yet, but that isn't relevant to the error. I can fix it on my end by changing the path to include .git, but this can easily confuse others (as the repo is present) --- 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. ---