* How do we handle the Sun Copyright for derivative works.
@ 2005-04-07 18:25 Steve Munroe
2005-04-07 20:24 ` Roland McGrath
0 siblings, 1 reply; 4+ messages in thread
From: Steve Munroe @ 2005-04-07 18:25 UTC (permalink / raw)
To: libc-hacker; +Cc: dgm69
How do we handle the Sun copyright in glibc code when we patch or
copy/modify such code. For example
./sysdeps/ieee754/dbl-64/s_logb.c.
1) Leave the Sun (C) and add 2005 date?
2) Leave the Sun (C) and add the LGPL header with 2005 date?
3) ?
Steven J. Munroe
Linux on Power Toolchain Architect
IBM Corporation, Linux Technology Center
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: How do we handle the Sun Copyright for derivative works.
2005-04-07 18:25 How do we handle the Sun Copyright for derivative works Steve Munroe
@ 2005-04-07 20:24 ` Roland McGrath
2005-04-07 21:02 ` Steve Munroe
0 siblings, 1 reply; 4+ messages in thread
From: Roland McGrath @ 2005-04-07 20:24 UTC (permalink / raw)
To: Steve Munroe; +Cc: libc-hacker, dgm69
> How do we handle the Sun copyright in glibc code when we patch or
> copy/modify such code. For example
> ./sysdeps/ieee754/dbl-64/s_logb.c.
>
> 1) Leave the Sun (C) and add 2005 date?
One never does this, AFAIK.
> 2) Leave the Sun (C) and add the LGPL header with 2005 date?
> 3) ?
What's the nature of the change? If it's small, then my tendency would be
just not to update the Sun copyright.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: How do we handle the Sun Copyright for derivative works.
2005-04-07 20:24 ` Roland McGrath
@ 2005-04-07 21:02 ` Steve Munroe
2005-04-07 21:14 ` Roland McGrath
0 siblings, 1 reply; 4+ messages in thread
From: Steve Munroe @ 2005-04-07 21:02 UTC (permalink / raw)
To: Roland McGrath; +Cc: dgm69, libc-hacker
Roland McGrath <roland@redhat.com> wrote on 04/07/2005 03:24:06 PM:
> > How do we handle the Sun copyright in glibc code when we patch or
> > copy/modify such code. For example
> > ./sysdeps/ieee754/dbl-64/s_logb.c.
> ...
>
> What's the nature of the change? If it's small, then my tendency would
be
> just not to update the Sun copyright.
Copy the file to sysdeps/powerpc/powerpc32/fpu and replace 1 line of code
with 8 lines of new code.
Steven J. Munroe
Linux on Power Toolchain Architect
IBM Corporation, Linux Technology Center
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: How do we handle the Sun Copyright for derivative works.
2005-04-07 21:02 ` Steve Munroe
@ 2005-04-07 21:14 ` Roland McGrath
0 siblings, 0 replies; 4+ messages in thread
From: Roland McGrath @ 2005-04-07 21:14 UTC (permalink / raw)
To: Steve Munroe; +Cc: dgm69, libc-hacker
> Roland McGrath <roland@redhat.com> wrote on 04/07/2005 03:24:06 PM:
>
> > > How do we handle the Sun copyright in glibc code when we patch or
> > > copy/modify such code. For example
> > > ./sysdeps/ieee754/dbl-64/s_logb.c.
> > ...
> >
> > What's the nature of the change? If it's small, then my tendency would
> be
> > just not to update the Sun copyright.
>
> Copy the file to sysdeps/powerpc/powerpc32/fpu and replace 1 line of code
> with 8 lines of new code.
If you are not modifying the old file, but adding a new one, then copy the
Sun copyright and add the normal libc LGPL header as well.
Thanks,
Roland
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2005-04-07 21:14 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-04-07 18:25 How do we handle the Sun Copyright for derivative works Steve Munroe
2005-04-07 20:24 ` Roland McGrath
2005-04-07 21:02 ` Steve Munroe
2005-04-07 21:14 ` Roland McGrath
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).