Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!zephyr!tektronix!tekgen!tekred!billr From: billr@tekred.CNA.TEK.COM (Bill Randle) Newsgroups: comp.sources.d Subject: Re: comp.sources.patches - END OF DISCUSSION Keywords: New group, comp.sources.patches Message-ID: <4075@tekred.CNA.TEK.COM> Date: 7 Jun 89 19:33:53 GMT References: <475@ssbell.UUCP> <480@ssbell.UUCP> <136@mcl.UUCP> <21559@mcdchg.chg.mcd.mot.com> <494@ssbell.UUCP> <25224@agate.BERKELEY.EDU> <141@dsinc.DSI.COM> Reply-To: billr@tekred.CNA.TEK.COM (Bill Randle) Organization: Tektronix, Inc., Redmond, OR Lines: 24 In article <141@dsinc.DSI.COM> syd@dsinc.UUCP (Syd Weinstein) writes: >In article <25224@agate.BERKELEY.EDU> wisner@mica.Berkeley.EDU (Bill Wisner) writes: >:Flame them to a smoldering crisp when they don't. >Rather than causing us to ignore you entirely, how about having the >moderators of the respective groups announce their willingness to >have the patches to us existing source coordinators. I have seen >a lot of posting about things, but have heard nothing official. > OK, consider this an official statement. I will gladly accept patches from authors or maintainers of sources that have been or will be posted to comp.sources.games. I will also give patches higher priority in posting than new stuff. I don't care how long after the original source posting you wait before sending me a patch or patches. I believe that timeliness is often most important if a "major" bug prevents lots of people from compiling or running a program. As an aside, I also plan to start using the "Patch-To:" auxillary header on new patch files submitted for posting. -Bill Randle Moderator, comp.sources.games Tektronix, Inc. games@saab.CNA.TEK.COM