[net.micro] General Solution to net.micro Subgroups Problem

knudsen (12/14/82)

Perhaps we can attack the problem of having too many sub-groups
for various machines by a different route, instead of either having
lots of stuff on the main .micro or spinning off .v20, .c64, .coco,
etc etc.

I propose we have one subgroup, micro.spec ("specific" or "special-purpose")
which would handle info of interest only to users of a particular machine.
Examples of what would go there:  Download protocols, machine-code patches
to PRINT in BASIC for CoCo, how to hook an Atari joystick to a V20, etc.

On the other hand, comments about a particular machine that would be of
interest to people in the shopping-around stage, these should stay in
net.micro, period.  Also the recent comments on brands of floppies.

In any event, choose your title carefully, so you (a) don't miss anyone
who should have read your article, and (b) don't get your name on the
mental blacklists of those who had to wade thru it just to see what
it was about.
For once, I'm not ashamed	mike k