This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: K6 patches for review
- To: "David S. Miller" <davem at dm dot cobaltmicro dot com>
- Subject: Re: K6 patches for review
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Mon, 24 Aug 1998 21:18:16 -0600
- cc: jfc at tiac dot net, egcs at cygnus dot com
- Reply-To: law at cygnus dot com
In message <199808250013.RAA28708@dm.cobaltmicro.com>you write:
> Date: Sun, 23 Aug 1998 20:53:53 -0600
> From: Jeffrey A Law <law@cygnus.com>
>
> It was for a target which is still covered by an NDA.
>
> Cygnus figured the MD_SCHED stuff would be useful to others and
> contributing it would not violate the NDA, so Cygnus went ahead and
> contributed the code.
>
> I heard this chip was released recently, does this mean the MD_SCHED_*
> support for it will be soon integrated into the tree?
Possibly. I don't have the contract in front of me to review for
confidentiality releases. And in many cases that's just the first
step that has to be taken before Cygnus contributes a port.
Contributions from Cygnus go through a conceptually simple process --
customers get the code first, after our customers have had it for
a while Cygnus contributes the code to egcs. That's the basic model.
We do make exceptions, for example infrastructure changes like MD_SCHED
can often go directly to egcs.
jeff