Date: Thu, 27 May 2004 17:08:16 -0700 From: Brooks Davis <brooks@one-eyed-alien.net> To: Marcel Moolenaar <marcel@xcllnt.net> Cc: src-committers@FreeBSD.org Subject: Re: cvs commit: src/lib/libc/net Makefile.inc eui64.3 eui64.c src/share/man/man5 Makefile eui64.5 src/sys/sys eui64.h src/tools/regression/lib/libc/net Makefile test-eui64.h test-eui64_aton.c test-eui64_line.c test-eui64_ntoa.c Message-ID: <20040528000816.GB18517@Odin.AC.HMC.Edu> In-Reply-To: <20040527224858.GA55573@ns1.xcllnt.net> References: <200405262258.i4QMw7KZ085659@repoman.freebsd.org> <20040527000844.GG55357@empiric.dek.spc.org> <20040527214958.GN23460@submonkey.net> <20040527220142.GA2636@Odin.AC.HMC.Edu> <20040527224858.GA55573@ns1.xcllnt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--OwLcNYc0lM97+oe1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 27, 2004 at 03:48:58PM -0700, Marcel Moolenaar wrote: > On Thu, May 27, 2004 at 03:01:43PM -0700, Brooks Davis wrote: > > >=20 > > > Is the copyright correct? For example: > > >=20 > > > # head -2 src/share/man/man5/eui64.5 > > > .\" Copyright (c) 1995 > > > .\" Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved. > >=20 > > I think so. The files with wpaul copyrights were all derived from > > files he wrote by copying them and editing them. I basicly changed > > the code to handle 8-byte strings instead of 6-byte ones (plus some > > extra flexability in the parsing) and changed the API to eliminate the > > old style non-thread safe functions. The main code and concept is > > his. There's definatly enough of his code there for it to have his > > copyright. I don't think there's enough new code to warrent adding mine > > (Aerospace's), but I will if someone how understands derivative works > > better says I should. >=20 > IANAL, but from a legal perspective it's probably better to add > your name to the copyright notice. Suppose there is no disclaimer of > warranty, then wpaul@ surely doesn't want to be held responsible > for this code, whether of not it was derived from his code. The > copyright probably also needs to be exact in terms of who owns > what part of the code in that case (to make sure it is known who is > liable when the faulty code construct is identified). I think the > basics do not change when there is a disclaimer of warranty, it's > just that most of the details become moot points since none of the > copyright holds are liable. >=20 > Just my unfounded take on this... I'd actually have to add a full new copyright block because I've got a particular wording that I must use (3-line BSD, but provided by my legal department). It would seem that under the existing block I'd be covered as a contributer, but IANAL. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --OwLcNYc0lM97+oe1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFAtoLvXY6L6fI4GtQRAtCbAJ9/T52ehIkppr9cOTNovNBcLzA8twCeMqTU ufqP0M+E1ANZpm9uYgfRAxY= =Z5Hg -----END PGP SIGNATURE----- --OwLcNYc0lM97+oe1--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040528000816.GB18517>