🚀 go-pugleaf

In article <1991Apr25.201646.13689@athena.mit.edu> jik@athena.mit.edu (Jonathan I. Kamens) writes:
>In article <1991Apr25.145012.25954@msuinfo.cl.msu.edu>, elliss@kira.egr.msu.edu (Stew Ellis) writes:
>|> I think that all posters of any sourcecode ought to
>|> include complete information on all particulars of hardware and software
>|> configuration of the systems that they have actually brought the package up
>|> on, and the difficulty of configuring for the known good targets, then a list
>|> of suspected or known difficult targets.
>

>  Perhaps the other source newsgroups can learn something from the new kid on
>the block. :-)

This is being done with the Environment: header line in comp.sources.games.
The Keywords: line has been used in the past but certain saves from rn can 
drop the Keywords: header.  I have considered using the Environment: line in 
comp.sources.misc.  It would have been useful in this situation had I known 
the limitation.

My questions are one of use. Should the Environment: line be adopted by 
comp.sources.misc ?  This question has probably been answered but I would
like to get some additional comments.  Next, when should the Environment:
header be used ? Always or just when the moderator is alerted to a limiting 
condition ?  Something in between ?  Anyone want to take a stab at a list
of standard keywords to be contained within this line ?

If there is something that I as moderator can do to format the postings
to make it easier for the users to deal with then let me know. I don't 
think that you will get much disagreement from me.  We just need to hash
out its usage and I will incorporate it into future postings to
comp.sources.misc.

			-Kent+

-- 
Kent Landfield                   INTERNET: kent@sparky.IMD.Sterling.COM
Sterling Software, IMD           UUCP:     uunet!sparky!kent
Phone:    (402) 291-8300         FAX:      (402) 291-4362
Please send comp.sources.misc-related mail to kent@uunet.uu.net.