From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11596 invoked by alias); 28 Sep 2009 17:30:00 -0000 Received: (qmail 11581 invoked by uid 22791); 28 Sep 2009 17:29:58 -0000 X-SWARE-Spam-Status: No, hits=-1.3 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from smtp19.orange.fr (HELO smtp19.orange.fr) (80.12.242.17) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 28 Sep 2009 17:29:52 +0000 Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf1912.orange.fr (SMTP Server) with ESMTP id C687320000B2; Mon, 28 Sep 2009 19:29:49 +0200 (CEST) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf1912.orange.fr (SMTP Server) with ESMTP id B8ED120000B7; Mon, 28 Sep 2009 19:29:49 +0200 (CEST) Received: from [192.168.127.10] (ARennes-252-1-60-196.w83-195.abo.wanadoo.fr [83.195.251.196]) by mwinf1912.orange.fr (SMTP Server) with ESMTP id 85BB720000B2; Mon, 28 Sep 2009 19:29:49 +0200 (CEST) From: "Yann E. MORIN" To: crossgcc@sourceware.org Subject: Re: croostool-ng: GCC 4.4.1 Working! Date: Mon, 28 Sep 2009 17:30:00 -0000 User-Agent: KMail/1.9.9 Cc: Joachim Nilsson References: <4AA39681.6040902@vmlinux.org> <200909262219.58158.yann.morin.1998@anciens.enib.fr> <4AC0BCD8.8090608@vmlinux.org> In-Reply-To: <4AC0BCD8.8090608@vmlinux.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200909281929.58890.yann.morin.1998@anciens.enib.fr> X-IsSubscribed: yes 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/msg00065.txt.bz2 Joachim, All, On Monday 28 September 2009 15:40:40 Joachim Nilsson wrote: > On 09/26/2009 10:19 PM, Yann E. MORIN wrote: > > 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=E9. > Sorry to hear that, I am not planning on abandonning crosstool-NG at all. I just wanted to say that it has been taking a lot of my time, it is in quite a good shape, I personnaly have no strong and big improvements I *need*, so development has slowed down. But I *will* *continue* to maintain and enhance it. > we are a lot of people who really appreciate your work! Thanks! :-) Having such feedback is part of the motivation to continue! > With your recent move to hg it could perhaps be easier to share=20=20 > the burden, so to speak? Yes, that was part of the plan. Submitting patches should be easier, now. With correctly formatted patches (eg. sent with the patchbomb extension to Hg, 'hg email'), it's very simple for me to apply and merge patches. > Are there anyone else out there willing to help Yann? In fact, the help I am most in need of is from people with needs I do not have: canadian, newlib, cygwin target, etc... so they push features and fixes to features I don't use and corner cases I don't hit. > I'm still learning, but I could at least start by reading up on hg and=20 > clone your tree. (I am a bit of a bzr and git man myself though, so I've= =20 > been lazy...) Well, I found Hg to be easier to learn than Git. I never seemed to understa= nd Git, while switching to Hg was quite straitghforward. > Maybe the best way for you would be if we set up a better patch approval= =20 > process? When a new patch is suggested (like mine), some other people=20 > start evaluating it and give it ++ or --, and if enough people approve=20 > your job is simply to pull it in? Not too unlike how Linus does it... That's a good idea, indeed. We could setup the following process: - post patch to crosgcc@sourceware... + cc: me - give a week (or so) for people to comment and rate with '+1' or '-1' (-1 requiring a comment). - after a week, require a majority of 2/3 to apply the patch: - if total_ratings < minimum, drop the patch, possibly with comments - else if ( positive_ratings / total_ratings ) > (2/3), then apply the pa= tch - else, drop the patch, possibly with comments (minimum is to be tweaked for this list: 10 may be just too many, while 3 may be not enough). I also receive patches directly, and for those patch I'd answer with smthg along the lines of: Please resend to crossgcc@... and cc me, or your patch will be dropped without furher notice. Do you guys find this approach to be sane? > > I'm a bit reluctant at applying your patch: there are currently 25 patc= hes > > 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=20 > buildroot guys had done it. I, perhaps wrongly, assumed they had=20 > already checked if existing patches had been applied upstream. I have it in a local clone, and it seems to work for my use-case. I will push later tonight. > > 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=20 > appropriate in this case. ;-) Bah, the manual is not so fine! ;-) Regards, Yann E. MORIN. --=20 .-----------------.--------------------.------------------.----------------= ----. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspira= cy: | | +0/33 662376056 | Software Designer | \ / CAMPAIGN | ___ = | | --=3D=3D< ^_^ >=3D=3D-- `------------.-------: X AGAINST | \e/ T= here is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspirac= y. | `------------------------------^-------^------------------^----------------= ----' -- For unsubscribe information see http://sourceware.org/lists.html#faq