Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!pasteur!ucbvax!decwrl!sun!wind!naughton
From: naughton%wind@Sun.COM (Patrick Naughton)
Newsgroups: comp.windows.x
Subject: Re: xlock enhancements
Summary: psuedo-flammage
Keywords: X11 Terminal Locker.
Message-ID: <59074@sun.uucp>
Date: 6 Jul 88 22:40:24 GMT
Expires: 6 Jul 88 22:40:23 GMT
References: <8807011345.AA20134@decwrl.dec.com>
Sender: news@sun.uucp
Reply-To: naughton@sun.com
Followup-To: comp.windows.x
Organization: Window Systems Group, Sun Microsystems, Mountain View
Lines: 25

The message Referenced above appeared on comp.windows.x on July 1st
without my prior knowledge.  This "vesper@3d.dec.com" person took it
upon him/herself to take a four month (two revision) old version of
xlock, make some changes to it and post it to the net. 

The source very clearly documented that I was maintaining this code and
that additions should be sent to me for integration, "Comments and
additions may be sent the author at:"...  The three other contributors
to xlock never had problems interpreting that simple statement over five
revisions. 

Ever since the poorly modified version of xlock appeared on the net, I
have been swamped with requests/complaints about "Which version is the
latest?"

The answer is this:
  Throw away the hacked V1.2 and wait a couple of days till I get a
chance to test V1.6 with vesper's changes integrated.  I'll post the
full file then, (the diffs would be as big as the file...  I never
released 1.5... too busy driving from NY to CA...). 

-Patrick
    ______________________________________________________________________
    Patrick J. Naughton				    ARPA: naughton@Sun.COM
    Window Systems Group			    UUCP: ...!sun!naughton
    Sun Microsystems, Inc.			    AT&T: (415) 336 - 1080