public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Joern Rennecke <joern.rennecke@superh.com>
Cc: gcc@gcc.gnu.org, gdb@sources.redhat.com
Subject: Re: SuperH patch contributions
Date: Fri, 17 Sep 2004 18:02:00 -0000	[thread overview]
Message-ID: <414B2629.2030409@gnu.org> (raw)
In-Reply-To: <200409171550.i8HFoKh31623@linsvr2.uk.superh.com>

I can't speak for GCC.

For GDB, ref:
http://sources.redhat.com/ml/gdb/2003-03/msg00064.html
I'd recommend creating a branch so that you can both post and commit the 
changes.  Good luck!

Andrew

> I am leaving SuperH, and on October the first, I am going to start with
> my new employment at ST Microelectronics.  I expect to continue to work
> on the SH gcc port there.  I have spoken with my manager
> (here at SuperH) what best to do with the current SuperH local patches,
> and we agreed that the best course of action is to post them on the
> gcc-patches / gdb-patches mailing lists.
> Our blanket copyright assignment on file with the FSF assigns copyright
> in changes and/or enhancements to the programs gcc, g++, gdb,
> binutils, libg++, libstdc++, dejagnu, GNU C++ testsuite and GNU C
> testsuite submitted by SuperH, Inc.
> Thus, by submitting these patches, the copyright assignment becomes
> effective for them.
> There will be some overlap between patches to different baselines.
> I think this is preferrable to missing important bits which might
> be lost and/or in uncertain copyright status if not submitted now.
> I am willing to answer questions on these patches, but won't have time
> for any significant code changes / merges now.  I hope to integrate
> some or most of these patches into the FSF mainline when I am at ST
> Microelectronics.


  reply	other threads:[~2004-09-17 18:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-17 15:50 Joern Rennecke
2004-09-17 18:02 ` Andrew Cagney [this message]
2004-09-21 10:33   ` Joern Rennecke
2004-09-21 13:02     ` Daniel Jacobowitz
2004-09-22 16:29       ` Andrew Cagney

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=414B2629.2030409@gnu.org \
    --to=cagney@gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=joern.rennecke@superh.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).