From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17432 invoked by alias); 28 Sep 2009 13:40:56 -0000 Received: (qmail 17414 invoked by uid 22791); 28 Sep 2009 13:40:54 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from vmlinux.org (HELO vmlinux.org) (193.41.214.66) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 28 Sep 2009 13:40:49 +0000 Received: from localhost (localhost [127.0.0.1]) by vmlinux.org (Postfix) with ESMTP id 9110D1DDA8AF; Mon, 28 Sep 2009 15:41:04 +0200 (CEST) Received: from vmlinux.org ([127.0.0.1]) by localhost (vmlinux.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3Bqh8p0cx85A; Mon, 28 Sep 2009 15:41:01 +0200 (CEST) Received: from [192.168.1.124] (90-224-113-214-no111.tbcn.telia.com [90.224.113.214]) by vmlinux.org (Postfix) with ESMTPSA id A483F1DDA89B; Mon, 28 Sep 2009 15:41:01 +0200 (CEST) Message-ID: <4AC0BCD8.8090608@vmlinux.org> Date: Mon, 28 Sep 2009 13:40:00 -0000 From: Joachim Nilsson User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.4pre) Gecko/20090915 Thunderbird/3.0b4 MIME-Version: 1.0 To: "Yann E. MORIN" CC: crossgcc@sourceware.org Subject: Re: croostool-ng: GCC 4.4.1 Working! References: <4AA39681.6040902@vmlinux.org> <4ABE32FF.70600@vmlinux.org> <200909262219.58158.yann.morin.1998@anciens.enib.fr> In-Reply-To: <200909262219.58158.yann.morin.1998@anciens.enib.fr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Mailing-List: contact crossgcc-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: crossgcc-owner@sourceware.org X-SW-Source: 2009-09/txt/msg00064.txt.bz2 On 09/26/2009 10:19 PM, Yann E. MORIN wrote: >> OK, so I don't want to sit on these patches any longer. > Yes, sorry... I have been a bit lazy the past few days (weeks) wrt > crosstool-NG... It's been threee years now I'm working on it, and > I feel a little bit blasé. Sorry to hear that, we are a lot of people who really appreciate your work! With your recent move to hg it could perhaps be easier to share the burden, so to speak? Are there anyone else out there willing to help Yann? I'm still learning, but I could at least start by reading up on hg and clone your tree. (I am a bit of a bzr and git man myself though, so I've been lazy...) Maybe the best way for you would be if we set up a better patch approval process? When a new patch is suggested (like mine), some other people start evaluating it and give it ++ or --, and if enough people approve your job is simply to pull it in? Not too unlike how Linus does it... > On Saturday 26 September 2009 17:27:59 Joachim Nilsson wrote: >> On 09/06/2009 01:01 PM, Joachim Nilsson wrote: >>> Anyway, I used the latest head (correct hg terminology?) of crosstool-ng >>> and added the 4.4.1 GCC patches from buildroot: >>> http://git.buildroot.net/buildroot/tree/toolchain/gcc/4.4.1 >>> That's about it. >>> How would I proceed in contributing these patches, inline attachments, >>> publish a Mercurial branch, or is it sufficient with the above pointer? > I'm a bit reluctant at applying your patch: there are currently 25 patches > applied to gcc-4.4.0, and I find it odd that 4.4.1 only requires 5. > I will try to forward-port the gcc-4.4.0 patchset up to 4.4.1. I see, I was a bit surprised myself when I started looking at how the buildroot guys had done it. I, perhaps wrongly, assumed they had already checked if existing patches had been applied upstream. > And to answer your question, the README has a quick step-by-step example > on how to submit patches. It boils down to using Mercurial's patchbomb > extension. Thanks, you're always too kind! A simple RTFM would have been appropriate in this case. ;-) Regards /Joachim -- For unsubscribe information see http://sourceware.org/lists.html#faq