public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com>
To: dewar@gnat.com
Cc: jbuck@synopsys.COM, jsm28@cam.ac.uk, mrs@windriver.com,
	gcc@gcc.gnu.org, Richard.Earnshaw@arm.com
Subject: Re: Copyright forms for new contributor?
Date: Mon, 22 Oct 2001 02:09:00 -0000	[thread overview]
Message-ID: <200110220908.KAA28096@cam-mail2.cambridge.arm.com> (raw)
In-Reply-To: <20011022023517.B724BF28AF@nile.gnat.com>

> 
> The FSU (Florida State University) copyrights are another matter. These
> do represent work done by Ted Baker's group at FSU. They cover the 
> tasking parts of the runtime, and neither FSU nor Ted wanted to 
> assign the copyright to FSF (Ted wanted specifically to have a clear
> record of the FSU involvement). I did discuss this with Richard Stallman
> at the time, and he indicated that he did not feel it was a problem. In
> the event that it does turn out to be a problem, we can simply remove
> the tasking runtime from the site, we will still have a working non-tasking
> port of GNAT if we do this. 

Shouldn't the runtime code be moved out into a separate directory, in the 
same way as other runtime code is (libstdc++, libjava, libobc ...).

Not only would this make it clearer what was part of the compiler and what 
was part of the run-time, but it would also be a step on the road to 
providing multi-lib support.

  reply	other threads:[~2001-10-22  2:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-21 19:35 dewar
2001-10-22  2:09 ` Richard Earnshaw [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-10-22  4:13 Richard Kenner
2001-10-16 17:53 mike stump
2001-10-16  8:46 mike stump
     [not found] <20011012115247.B25697@tornado.cygnus.com>
     [not found] ` <20011012174437.B10341@linux11.lxfarm.csc.liv.ac.uk>
     [not found]   ` <20011012125150.C25999@tornado.cygnus.com>
     [not found]     ` <20011012190633.C10341@linux11.lxfarm.csc.liv.ac.uk>
     [not found]       ` <20011012142725.A26727@tornado.cygnus.com>
     [not found]         ` <20011015112854.A8793@linux11.lxfarm.csc.liv.ac.uk>
     [not found]           ` <20011015095852.D22414@tornado.cygnus.com>
     [not found]             ` <20011015162207.A17825@linux11.lxfarm.csc.liv.ac.uk>
     [not found]               ` <20011015114013.A23365@tornado.cygnus.com>
     [not found]                 ` <20011015173305.B17825@linux11.lxfarm.csc.liv.ac.uk>
2001-10-15  9:39                   ` Diego Novillo
2001-10-16  1:38                     ` Gerald Pfeifer
2001-10-16 12:47                       ` Joe Buck
2001-10-16 13:33                         ` Florian Weimer
2001-10-16 13:43                           ` Diego Novillo
2001-10-16 14:03                             ` Joe Buck
2001-10-16 13:54                         ` Joseph S. Myers
2001-10-16 14:08                           ` Joe Buck
2001-10-17 12:21                         ` Gerald Pfeifer
2001-10-17 17:42                           ` Carlo Wood
2001-10-16 15:09                     ` Craig Rodrigues
2001-10-16 19:38                       ` Joe Buck

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=200110220908.KAA28096@cam-mail2.cambridge.arm.com \
    --to=rearnsha@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=dewar@gnat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jbuck@synopsys.COM \
    --cc=jsm28@cam.ac.uk \
    --cc=mrs@windriver.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).