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 BA8B0200C7D for ; Tue, 2 May 2017 03:55:28 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id B92C2160BC2; Tue, 2 May 2017 01:55:28 +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 02B88160BC1 for ; Tue, 2 May 2017 03:55:27 +0200 (CEST) Received: (qmail 64362 invoked by uid 500); 2 May 2017 01:55:27 -0000 Mailing-List: contact issues-help@eagle.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@eagle.apache.org Delivered-To: mailing list issues@eagle.apache.org Received: (qmail 64353 invoked by uid 99); 2 May 2017 01:55:27 -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, 02 May 2017 01:55:27 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id F3A27E0667; Tue, 2 May 2017 01:55:26 +0000 (UTC) From: asdf2014 To: issues@eagle.apache.org Reply-To: issues@eagle.apache.org References: In-Reply-To: Subject: [GitHub] eagle issue #925: [EAGLE-1012] Some language level problems in `eagle-core` ... Content-Type: text/plain Message-Id: <20170502015526.F3A27E0667@git1-us-west.apache.org> Date: Tue, 2 May 2017 01:55:26 +0000 (UTC) archived-at: Tue, 02 May 2017 01:55:28 -0000 Github user asdf2014 commented on the issue: https://github.com/apache/eagle/pull/925 If these improvements are necessary, we should step by step merge to avoid too much code conflict. So, creating multiple sub `PRs` for `EAGLE-1012` will be more suitable for this situation. What do you think? @jhsenjaliya @qingwen220 --- 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. ---