This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: How do we handle the Sun Copyright for derivative works.

From: Roland McGrath <roland at redhat dot com>
To: Steve Munroe <sjmunroe at us dot ibm dot com>
Cc: dgm69 at us dot ibm dot com, libc-hacker at sources dot redhat dot com
Date: Thu, 7 Apr 2005 14:13:58 -0700
Subject: Re: How do we handle the Sun Copyright for derivative works.

> 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

References:
- Re: How do we handle the Sun Copyright for derivative works.
  - From: Steve Munroe

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]