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 0ACB018A6A for ; Wed, 1 Jul 2015 20:23:39 +0000 (UTC) Received: (qmail 1851 invoked by uid 500); 1 Jul 2015 20:23:38 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 1785 invoked by uid 500); 1 Jul 2015 20:23:38 -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 1772 invoked by uid 99); 1 Jul 2015 20:23:38 -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; Wed, 01 Jul 2015 20:23:38 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 4A3DAE03C8; Wed, 1 Jul 2015 20:23:38 +0000 (UTC) From: wilderrodrigues To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack pull request: CLOUDSTACK-8180 - RouterVM does no longer... Content-Type: text/plain Message-Id: <20150701202338.4A3DAE03C8@git1-us-west.apache.org> Date: Wed, 1 Jul 2015 20:23:38 +0000 (UTC) Github user wilderrodrigues commented on the pull request: https://github.com/apache/cloudstack/pull/549#issuecomment-117815608 Yep... Agree. That's what I also suggested in my reply. We are getting better... Next one will be perfect. :) Thanks, guys! Cheers, Wilder Sent from my iPhone On 01 Jul 2015, at 22:17, Remi Bergsma > wrote: I agree, ticket id is enough. Sent from my iPhone > On 01 Jul 2015, at 21:35, Miguel Ferreira > wrote: > > @wilderrodrigues @remibergsma @bhaisaab why not just put the the ticket ID in the commit message? > something like: > > CLOUDSTACK-8180: adding this > CLOUDSTACK-8180: changing that > — > Reply to this email directly or view it on GitHub. > — 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. ---