From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24552 invoked by alias); 30 Nov 2012 00:39:12 -0000 Received: (qmail 24540 invoked by uid 22791); 30 Nov 2012 00:39:11 -0000 X-SWARE-Spam-Status: No, hits=-3.0 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED X-Spam-Check-By: sourceware.org Received: from toast.topped-with-meat.com (HELO topped-with-meat.com) (204.197.218.159) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 30 Nov 2012 00:39:07 +0000 Received: by topped-with-meat.com (Postfix, from userid 5281) id 85C6E2C0D0; Thu, 29 Nov 2012 16:39:06 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Roland McGrath To: David Holsgrove Cc: Joseph Myers , "libc-ports@sourceware.org" , John Williams , "edgar.iglesias@gmail.com" , Vinod Kathail , Tom Shui , Vidhumouli Hunsigida , Nagaraju Mekala Subject: RE: [PATCH] MicroBlaze Port In-Reply-To: David Holsgrove's message of Friday, 30 November 2012 00:15:53 +0000 <91de6cb7-e54f-401d-8159-591a93f26d1f@VA3EHSMHS024.ehs.local> References: <1354168245-14527-1-git-send-email-david.holsgrove@xilinx.com> <91de6cb7-e54f-401d-8159-591a93f26d1f@VA3EHSMHS024.ehs.local> Message-Id: <20121130003906.85C6E2C0D0@topped-with-meat.com> Date: Fri, 30 Nov 2012 00:39:00 -0000 X-CMAE-Score: 0 X-CMAE-Analysis: v=2.0 cv=LtfpOghc c=1 sm=1 a=Z6MIti7PxpgA:10 a=kj9zAlcOel0A:10 a=hOe2yjtxAAAA:8 a=14OXPxybAAAA:8 a=U0oTm8cWUwAA:10 a=I3qt74UO_b6rVBoYg58A:9 a=CjuIK1q_8ugA:10 a=WkljmVdYkabdwxfqvArNOQ==:117 X-IsSubscribed: yes Mailing-List: contact libc-ports-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: libc-ports-owner@sourceware.org X-SW-Source: 2012-11/txt/msg00143.txt.bz2 Being in the ports/ tree is no different from being a separate add-on port. So you can update your code and test it against the trunk that way. For the items where Joseph suggested the clean solutions would involve some change to the main tree, you can work on each of those patches and post it without delay. We'll decide case-by-case whether each one is safe enough to commit during the freeze. elf.h additions will be fine, for example. If it turns out that all the changes you need outside your own port are safe enough to let in during the 2.17 freeze, then your port can make 2.17 too. But we'll have to take it one change at a time and see how it goes. Thanks, Roland