delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2000/11/07/11:30:39

Date: Tue, 7 Nov 2000 11:28:57 -0500
Message-Id: <200011071628.LAA10566@envy.delorie.com>
X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp AT delorie DOT com
In-reply-to: <20001107102617.A18988@kendall.sfbr.org> (message from JT
Williams on Tue, 7 Nov 2000 10:26:17 -0600)
Subject: Re: copyright notice in source
References: <20001107102617 DOT A18988 AT kendall DOT sfbr DOT org>
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com

> even *want* a copyright?  I'm not looking for legal counsel---I just
> got to wondering if I should add my own (C) to some source I've hacked
> on and (IMHO) improved.

Minor changes usually don't need a separate copyright notice.  If you
make a major change to djgpp source, you should send me the
appropriate legal papers first, either to disclaim copyright or assign
it to me.  In a few cases where the licenses are compatible, we've
kept the original copyright notice (the script that puts my (c) on
them looks for existing copyright notices if it can, and tries to
avoid those files) for files copied from other sources (like the BSD
files).

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019