From: Roland McGrath <roland@redhat.com>
To: Steve Munroe <sjmunroe@us.ibm.com>
Cc: libc-hacker@sources.redhat.com, dgm69@us.ibm.com
Subject: Re: How do we handle the Sun Copyright for derivative works.
Date: Thu, 07 Apr 2005 20:24:00 -0000 [thread overview]
Message-ID: <200504072024.j37KO6C4016839@magilla.sf.frob.com> (raw)
In-Reply-To: Steve Munroe's message of Thursday, 7 April 2005 13:25:37 -0500 <OF34DC79C6.181DCD01-ON86256FDC.00649B0B-86256FDC.00653A0B@us.ibm.com>
> 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.
next prev parent reply other threads:[~2005-04-07 20:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-07 18:25 Steve Munroe
2005-04-07 20:24 ` Roland McGrath [this message]
2005-04-07 21:02 ` Steve Munroe
2005-04-07 21:14 ` Roland McGrath
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=200504072024.j37KO6C4016839@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=dgm69@us.ibm.com \
--cc=libc-hacker@sources.redhat.com \
--cc=sjmunroe@us.ibm.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).