🚀 go-pugleaf

andy@cbmvax (Andy Finkel) writes:
>valentin@cbmvax (Valentin Pepelea) writes:
>>danbabcock@eklektik.UUCP (/dev/ph1) writes:
>>>
>>> The following are two bug/feature reports that I emailed
>>> to Commodore. I'm posting them because I'm sure some other
>>> people are interested, and I'm not sure if Commodore
>>> received my email (no response as of this writing).
>>
>> If you mailed the bug reports to bugs@cbmvax, chances are
>> the mail was received.  But you did not get a reply,
>> because no reply was ever sent to you. It would be
>> ideal for bugs@cbmvax to reply to you with the bug number
>> that was assigned to your report, but alas that is not the
>> case.
>
> Sorry, he has no idea what he's talking about.

Now children, don't quarrel in-house; go out on the net to
play.

Oops!  Wrong newsgroup!  Thought I was in misc.kids.  ;-)

> We do a reply on emailed bug messages as an ACK before
> it's entered in the database, but rely on the return
> address being accurate.  They seem to bounce a lot :-(

Now there at least is an easy problem to solve!  Take a
page from the vote takers' manual; if your ACKs bounce,
bulk post them!

I think _everybody_ would like to see a monthly posting
of new bug-number, bug-reported-by, bug-assigned-to,
bug-priority, bug-one-line-descriptions from CBM show up
in comp.sys.amiga.tech, and the load as a percent of the
newsgroup volume would be infinitessimal.

Add to that a list of known outstanding bugs, and known fixed
bugs with fixes not yet released, and it would be a lot easier
to decide whether to report the latest quirky behavior seen in
AmigaDOS 1.1.  ;-)

If someone at CATS has the time, that would be a good PR and
public service kind of a thing to do on USENet, and would
save developers and users mountains of time figuring out that
the problem is in the OS, and not in our stars.

Kent, the man from xanth.
<xanthian@Zorch.SF-Bay.ORG> <xanthian@well.sf.ca.us>