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 DD77A200C1A for ; Mon, 13 Feb 2017 17:14:01 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id DC0AA160B60; Mon, 13 Feb 2017 16:14:01 +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 2A530160B4D for ; Mon, 13 Feb 2017 17:14:01 +0100 (CET) Received: (qmail 56694 invoked by uid 500); 13 Feb 2017 16:14:00 -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 56683 invoked by uid 99); 13 Feb 2017 16:13:59 -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, 13 Feb 2017 16:13:59 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id CA6E2DFC2F; Mon, 13 Feb 2017 16:13:59 +0000 (UTC) From: swill To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: =?utf-8?q?=5BGitHub=5D_cloudstack-www_issue_=2334=3A_Remove_link_to_=E2=80=9Cplanet=2Eapache=2Eorg=E2=80=9D_and_update_=2E=2E=2E?= Content-Type: text/plain Message-Id: <20170213161359.CA6E2DFC2F@git1-us-west.apache.org> Date: Mon, 13 Feb 2017 16:13:59 +0000 (UTC) archived-at: Mon, 13 Feb 2017 16:14:02 -0000 Github user swill commented on the issue: https://github.com/apache/cloudstack-www/pull/34 Yes @rafaelweingartner, that is also my concern. It **probably** would be fine because the `.gitignore` would handle the problem cases with the merges (I hope), but it would make it less obvious to the end user what was going on for sure. --- 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. ---