MK> "back in 82"?
Yes, the paper manuals we had at the university back in the 1980's.
MK> Sure, coreutils man pages provide a bug reporting address -- and
MK> no information about how to usefully report a bug. (And, as a
Indeed, I recall often mailing such addresses gets 'subscribers only' replies.
I like on Debian where we can just do
$ reportbug -f
-f FILENAME, --filename=FILENAME
Report a bug in the package containing FILENAME so you don't
have to figure out what package the file belongs to. The path
will be searched for an exact path for FILENAME before attempt-
ing to broaden the search to all files.
But that doesn't go direct to upsteam.
I know: have an extra database of all the 'items' and where to report
bugs for each...
Hmmm, emacs parts have ";; This file is part of GNU Emacs.".
Maybe something that goes along with the copyright that says where to
report bugs. Naaa, often copyrights are just a symlink to one or two
files for the whole system.
Anyway, to pass "ISO 9001 Quality Awards" sooner or later every
component needs a maintainer or contact address. No more 'mysterious
suitcase near the second level washroom'.
OK, thanks for continuing to ponder this. No hurry.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
