Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rutgers!mcnc!uvaarpa!murdoch!astsun.astro.Virginia.EDU!gsh7w
From: gsh7w@astsun.astro.Virginia.EDU (Greg Hennessy)
Newsgroups: comp.unix.shell
Subject: Re: ksh 11/16/88e now available in AT&T Toolchest
Message-ID: <1990Oct2.224810.1547@murdoch.acc.Virginia.EDU>
Date: 2 Oct 90 22:48:10 GMT
References: <4140@lib.tmc.edu> <1990Oct2.180301.10897@cs.utk.edu> <4143@lib.tmc.edu>
Sender: news@murdoch.acc.Virginia.EDU
Followup-To: gnu.misc.discuss
Organization: University of Virginia
Lines: 25

Followups to gnu.misc.discuss, since this has little to do with unix
shells. 

Jay Maynard writes:
#Your statement is only true if you also hold to the belief that placing their
#code in your code automatically turns your code into their code. There's only
#one word that correctly describes that scenario: theft. The FSF has
#stolen your 
#code, and turned it into their code, all by a couple of innocuous-sounding
#lines in the GNU Public Virus...er...License.

Are you spreading misinformation through ingorance or malice? While I
don't speak for the FSF, the FSF does not consider that using FSF code
makes your code become theirs. If you use their code in your programs,
the copyright belongs to you both. If you wish to distribute this
code, you have to do so in a mutually agreeable form. The FSF tells
you up front what their terms are. 

What the FSF is doing is by no stretch of the imagination theft.

--
-Greg Hennessy, University of Virginia
 USPS Mail:     Astronomy Department, Charlottesville, VA 22903-2475 USA
 Internet:      gsh7w@virginia.edu  
 UUCP:		...!uunet!virginia!gsh7w