Path: utzoo!utgpu!attcan!uunet!seismo!sundc!pitstop!sun!amdahl!drivax!frotz From: frotz@drivax.UUCP (Frotz) Newsgroups: comp.binaries.ibm.pc.d Subject: Re: bugs Message-ID: <3963@drivax.UUCP> Date: 10 Nov 88 19:37:43 GMT References: <4648@bsu-cs.UUCP> <36085@clyde.ATT.COM> <4670@bsu-cs.UUCP> Reply-To: frotz@drivax.UUCP (Frotz) Organization: Digital Research, Inc., Monterey, California Lines: 16 In article <4670@bsu-cs.UUCP> dhesi@bsu-cs.UUCP (Rahul Dhesi) writes: >If I find some shortcomings (ahem) in a submission, which of the >following two alternatives is better? > >-- posting it and simply documenting bugs that I find > >-- or not posting it and sending feedback to the author and waiting for >him to either fix it or ask me to go ahead and post anyway My vote is for: a) requesting information from the author on small packages. (If I were the author, I would want to know that something was wrong with my small(>20K) utility.) b) sending out bug reports on (>20K) medium to large packages. Frotz