From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23994 invoked by alias); 11 Jul 2006 00:15:45 -0000 Received: (qmail 23985 invoked by uid 22791); 11 Jul 2006 00:15:44 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Tue, 11 Jul 2006 00:15:41 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1G05ud-0000w5-6Z; Mon, 10 Jul 2006 20:15:39 -0400 Date: Tue, 11 Jul 2006 00:15:00 -0000 From: Daniel Jacobowitz To: Maxim Grigoriev Cc: gdb@sourceware.org Subject: Re: Tensilica would like to submit an XTENSA GDB patch Message-ID: <20060711001539.GC3232@nevyn.them.org> Mail-Followup-To: Maxim Grigoriev , gdb@sourceware.org References: <44B2DBC8.90608@hq.tensilica.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44B2DBC8.90608@hq.tensilica.com> User-Agent: Mutt/1.5.11+cvs20060403 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/msg00030.txt.bz2 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. -- Daniel Jacobowitz CodeSourcery