From: Maxim Grigoriev <maxim@tensilica.com>
To: Robert Dewar <dewar@adacore.com>
Cc: Maxim Grigoriev <maxim@tensilica.com>,
gdb@sourceware.org, Nick Roberts <nickrob@snap.net.nz>
Subject: Re: Tensilica would like to submit an XTENSA GDB patch
Date: Tue, 11 Jul 2006 00:05:00 -0000 [thread overview]
Message-ID: <44B2EB55.7090503@hq.tensilica.com> (raw)
In-Reply-To: <44B2DC5E.5000303@adacore.com>
Robert, Nick, thanks much for your replies,
>> 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.
>
> Step one, file a proper copyright assignment form. Copies of this form
> may be obtained from the Free Software Foundation (they are not
> available on line).
I think it's already done.
Please, let me know if I need to refile it ( the previous one was sent
some time ago ).
-- Maxim
next prev parent reply other threads:[~2006-07-11 0:05 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 [this message]
2006-07-11 0:08 ` Daniel Jacobowitz
2006-07-11 0:15 ` Daniel Jacobowitz
[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=44B2EB55.7090503@hq.tensilica.com \
--to=maxim@tensilica.com \
--cc=dewar@adacore.com \
--cc=gdb@sourceware.org \
--cc=nickrob@snap.net.nz \
/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