Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Maxim Grigoriev <maxim@tensilica.com>
Cc: gdb@sourceware.org
Subject: Re: Tensilica would like to submit an XTENSA GDB patch
Date: Tue, 11 Jul 2006 00:15:00 -0000	[thread overview]
Message-ID: <20060711001539.GC3232@nevyn.them.org> (raw)
In-Reply-To: <44B2DBC8.90608@hq.tensilica.com>

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


  parent reply	other threads:[~2006-07-11  0:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-10 22:59 Maxim Grigoriev
2006-07-10 23:01 ` Robert Dewar
2006-07-10 23:08   ` Nick Roberts
2006-07-11  0:02   ` Petr Vandrovec
2006-07-11  0:12     ` Daniel Jacobowitz
2006-07-11  0:05   ` Maxim Grigoriev
2006-07-11  0:08     ` Daniel Jacobowitz
2006-07-11  0:15 ` Daniel Jacobowitz [this message]
     [not found]   ` <44B2F3D8.3040000@hq.tensilica.com>
2006-07-11  0:44     ` Maxim Grigoriev
2006-07-11  0:50 Maxim Grigoriev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060711001539.GC3232@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=maxim@tensilica.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox