From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5760 invoked by alias); 11 Jul 2006 00:50:07 -0000 Received: (qmail 5705 invoked by uid 22791); 11 Jul 2006 00:50:04 -0000 X-Spam-Check-By: sourceware.org Received: from hq.tensilica.com (HELO mailapp.tensilica.com) (65.205.227.29) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 11 Jul 2006 00:50:00 +0000 Received: from localhost ([127.0.0.1] ident=amavis) by mailapp.tensilica.com with esmtp (Exim 4.34) id 1G06Rr-00006S-3O; Mon, 10 Jul 2006 17:49:59 -0700 Received: from mailapp.tensilica.com ([127.0.0.1]) by localhost (mailapp [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 32622-03; Mon, 10 Jul 2006 17:49:58 -0700 (PDT) Received: from maxim_fc3.hq.tensilica.com ([192.168.11.68]) by mailapp.tensilica.com with esmtp (Exim 4.34) id 1G06Rq-00006M-Nm; Mon, 10 Jul 2006 17:49:58 -0700 Message-ID: <44B2F5B6.3060700@hq.tensilica.com> Date: Tue, 11 Jul 2006 00:50:00 -0000 From: Maxim Grigoriev User-Agent: Thunderbird 1.5 (X11/20051201) MIME-Version: 1.0 To: Daniel Jacobowitz , gdb@sourceware.org, Maxim Grigoriev Subject: Re: Tensilica would like to submit an XTENSA GDB patch Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-07/txt/msg00032.txt.bz2 Hi Daniel, > You've already been referred to the CONTRIBUTE file Yes, I got it. So I'm going to follow this instruction. > One of the most important things when submitting a new port is to start > by submitting each fix to the generic (target-independent) portion of > GDB, with an explanation of why it is necessary. If you just post a > single large patch, no one will be interested in reviewing it. Thanks much for the explanation. It helps to understand the process. My first update doesn't include any target-independent code. In the future, I'd expect us to have some generic fixes for the problems exposed by XTENSA users. But, it doesn't seem to be an issue right now. > If you intend to continue maintaining it, then yes. If not we probably > would reject the contribution. It's of no use if no one is keeping it up to date. Yes, we're highly interested in maintaining it. Thanks, Maxim Daniel Jacobowitz wrote: > On Mon, Jul 10, 2006 at 03:59:20PM -0700, Maxim Grigoriev wrote: > >> Hi, >> >> My email addresses GDB maintainers. >> >> I merged GDB Tensilica local changes with GDB 6.5, and it works fine. >> We'd like to submit XTENSA port and start monitoring it. It would >> benefit both us and our customers. Once in while, Tensilica tried to >> submit an XTENSA port, but it didn't work out for some reason. >> >> So if this is possible can somebody among GDB maintainers start >> working with me, please ? >> >> I'll probably need a short instruction or a reference to the right >> document describing how to submit GDB patches. >> > > You've already been referred to the CONTRIBUTE file; it's fairly > useful. You can also find lots of examples in the mailing list > archives for the gdb-patches mailing list. > > One of the most important things when submitting a new port is to start > by submitting each fix to the generic (target-independent) portion of > GDB, with an explanation of why it is necessary. If you just post a > single large patch, no one will be interested in reviewing it. > > We're always short of maintainer time, but we do the best we can > to see that patches get looked at. > > >> And, question: If I succeed with submitting XTENSA port, should I >> become a maintainer for the XTENSA-specific code ? >> > > If you intend to continue maintaining it, then yes. If not we probably > would reject the contribution. It's of no use if no one is keeping it > up to date. > >