Path: utzoo!attcan!uunet!van-bc!mdivax1!mitchell Newsgroups: comp.misc Subject: Re: The jargon file version 2.3.1 03 JAN 1991 follows in 11 parts Message-ID: <1991Jan14.150431.364@mdivax1.uucp> Date: 14 Jan 91 15:04:31 GMT References: <1991Jan4.194312.14418@erg.sri.com> <1633@inews.intel.com> <612@necssd.NEC.COM> Reply-To: mdivax1!bb29c!mitchell (Bill Mitchell) Organization: Mobile Data International Lines: 26 Return-Path: Apparently-To: van-bc!rnews In article <612@necssd.NEC.COM> harrison@necssd.NEC.COM (Mark Harrison) writes: >In article <1633@inews.intel.com>, bhoughto@pima.intel.com (Blair P. Houghton) writes: > >> #pragma project_to_the_back_of_the_theatre > >> CONSEQUENTLY, I WOULD EXPECT THAT THE NEXT TIME ERIC POSTS >> ABOUT IT, HE'LL BE KIND ENOUGH SIMPLY TO STATE THAT IT IS >> AVAILABLE AND WHERE AND HOW TO GET IT AND NOT POST THE >> ENTIRE TEXT WHICH IS SOMETHING OF AN ABOMINABLE PRACTICE >> IN THE _FIRST_ PLACE. > >#pragma me_too > >NO NO NO, NOT ALL OF US HAVE ACCESS TO FTP!!!! POSTING THE TEXT IS >*JUST FINE!* >-- Let me add a qualified ME_TOO to this. I too lack FTP access. Because of this, I appreciate having the entire text posted where I can get at it. However, I'm not a contributor, and I do not need a copy of the complete jargon file at every revision. Perhaps there is a workable compromise solution?? If there is no workable compromise, I'd rather see the entire file posted with each revision than not see anything. -- mitchell@mdi.com (Bill Mitchell)