🚀 go-pugleaf

	[ First, a word from your moderator:

	  info-gnu-fortran@prep.ai.mit.edu is now being moderated on
	  the same basis as other GNU info-* lists.  The list is now
	  being filtered to remove items meant for
	  info-gnu-fortran-request, that can be answered by the
	  moderator without bothering the list, or should have been
	  sent to another list.

	  enjoy -len 
	]

Five things:

    1. Send requests to be on or off the GNU Fortran Mailing List to:

          info-gnu-fortran-request@prep.ai.mit.edu

    2. Note the "prep" in place of the "gnu".  Both will work for a long
       time, but "prep" is better.  info-gnu-fortran is homed on prep
       and mailing directly there will save time and resources.

    3. Do not send any requests or comments or questions regarding the
       list to info-gnu-fortran@prep.ai.mit.edu (or @gnu...), send
       them to info-gnu-fortran-request@prep.ai.mit.edu instead.
       Furthermore, don't send anything to me (burley@gnu.ai.mit.edu)
       unless you really want to take the GNU Fortran author's time
       and thus delay the project -- especially since I can't add or
       remove anyone to or from the mailing list.  I am as always
       willing to answering reasonable questions, but I'm just making
       it clear what effect that has on the project.

    4. Don't expect that comments in your request like "contact us when you
       want a beta tester" will be honored in precisely the way you might
       expect -- we are going to notify _everyone_ on the list when some form
       of testing is to begin, and ask for "volunteers" then.  I'm sure
       the mailing list maintainer doesn't mind (and I don't mind when I see
       the confirmation email from him/her) seeing the info, so it's ok to
       send, but it worries me that some of you might be thinking we're
       keeping a matrix of who wants to do what testing on which machines.
       We're not.  I'm not even sure I know what a matrix is.  I'm just
       writing a Fortran compiler, not Fortran code, you see.

    5. It looks like all my earlier posts got out after all, so there were
       multiple copies, precisely the sort of thing I wished to avoid by
       cross-posting.  However I've come to the conclusion that this happened
       because one of the groups to which I originally cross-posted was
       moderated, and thus held up the post to all three groups until the
       article was approved.  So, I'm cross-posting this article and do not
       intend to worry about not seeing this until sometime later in the week.

    6. There is no sixth thing.  Read the first line again.

--

James Craig Burley, Software Craftsperson    burley@gnu.ai.mit.edu